20 Fundamentals for a Successful Test Automation Infrastructure BY YONI FLENNER

Identify Page Elements (text fields, buttons, link etc.) and configure them in a certain class, in which you can implement functions that will perform several operations. For example: inserting text and clicking on a button by identifying the element beforehand – which is called Page Object.
Write a mechanism that will be activated when a test fails.
Write another mechanism to return the page to a certain point (for example: the main page) in order to create independent tests.
Develop a report module and implement a report module for the executed automated tests.
Add to the reports screenshots and recordings when tests fail.
Implement the project in a way that will allow reading all parameters from external configuration files (for example: the location to save the reports).
Incorporate Visual Testing for image comparison to test if the site looks as it is supposed to (for example: if a field moved by 6 pixels to the right, the test will fail).
Create Cross-browser compatibility.
Write log files to save information for the developers which will also include stack trace and other details from the exceptions, which will show up in case of a failed test.
Object Repository – implement also a central place in which you’ll identify all of the elements’ properties in the application.
Connect the system’s database to execute queries and draw information (Despite not having access to the application’s database, we can easily create a simulation for a portfolio).
Implement the Data Driven Testing (DDT) method to read from CSV/ Excel files.
Implement the Keyword Driven Testing (KDT) or BDD methods with Gherkin language.
Create support for parallel testing on different environments.
Connection to external libraries (for example: interface cloud services API such as YouTube)
Create support for scheduling execution and interface CI systems (it’s possible to install Jenkins on the computer and working with it).
Compatibility with Mobile device platforms.
Expand to a compatibility with Desktop Apps.
The test automation infrastructure should be written according to known Design Patterns, Clean Code methods, coding conventions that must be configured at the design level.
Finally, documentation of the entire procedure from A to Z. The list clearly shows how Selenium is a very small component of the automation testing project.

Web App QA Automation with Selenium

Programming language - Java - Java for Testers
Selenium
TestNG
Gradle
Jenkins

REST API Automation with Rest-Assured

Programming language - Java - Java for Testers
Concepts: HTTP, REST API
TestNG
Rest Assured Framework - Github - A Guide to REST-assured
Gradle
Jenkins

Test Automation Best Practices Read Detail

Create An Automation Plan
Identify Test Cases That Can Be Automated
Develop Test Cases
Test Early And Frequently
Choose Appropriate Automated Testing Software And Tool
Segregate Your Automated Testing Skills And Efforts
Create Test Data
Create Test Cases That Are Reusable And Easy To Maintain

Android Test Automation Framework

https://essenceoftesting.blogspot.sg/2017/02/features-of-my-android-test-automation.html https://essenceoftesting.blogspot.sg/2017/02/sharing-implementation-of-cucumber-jvm.html https://essenceoftesting.blogspot.sg/2017/02/features-of-my-android-test-automation.html

Automated Test has the following benefits.

You can conduct more testing in a faster way.
You can run existing test scenario on many times by using automated test with same input and timing for each run.
Tester can spend more time in a smarter way to find bugs rather than concentrating on input and observing the result.
You can save the test object and rerun afterwards. The incremental cost to run automated test in negligible. Also, you have a better chance to find new bugs that may be introduced for changed software.
Many bugs are found when the system is run for long hours. That can be achieved more smartly by automated testing compared to manual testing.
Testing efficiency is the measurement of test that a tester runs in an hour. Higher efficiency lowers product development time and costs.
Testing effectiveness is the rate rate at which you can find bugs before software is released. Higher effectiveness produces better product with lesser cost and provides more customer satisfaction.
If you replace manual testing with automated test, that can reduce your testing time significantly. In the long run, it reduces your time to market the product and results in enormous cost benefit.
Earlier entry of the product in the market means that you have bigger share of the market. So you can achieve a greater margin of profit in the end.
Higher market share means lower unit cost. Higher volume means bigger discounts from the supplier and better operating efficiency.
Tester's toolbox
A curated list of awesome test automation frameworks, tools, libraries, and software for different programming languages.