THE

Testing HemispherE

Software Testing is a Globe, where you have 2 hemispheres.

One is Manual and the other is Automation. Most companies have both automated and manual testing efforts together. You might disagree but the fact is "there needs to be balanced Automated and Manual test approach for a process/product triumph."

High-quality productivity comes in when your manual test engineers have created a complete set of test cases that have immense traceability and test coverage, and then your automation engineers have automated your smoke & regression test cases.

Software Testing || QA

Test Automation || Product Testing

Continuous Integration || Regression Testing

Rubber Stamping Ideas in Software Testing

Rubber Stamping in Software Testing >> Re-Usability/Framework Usability in Automation.

1. The test scripts will be less expensive due to the better rubber stamping.
2. Modification to the test scripts won’t affect the test data.
3. Healthier rubber-stamping is attained only when the scripts are organized properly.
4. Open to any Test Tool.
5. Test cases can be performed with ample number of data when rubber stamping is fittingly used.
6. Simple script management.
7. Independent of Application under test and same script works for every level of testing.
8. Testing can be planned with/without AUT (Application Under Test).
9. It offers notable (Depends on type of framework).
10. Range of test scenarios can be executed by changing the test data in the external data (as most of us use xls file).

Prologue >> Automation Testing

What is Automation Testing?

Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions. Commonly, test automation involves automating a manual process already in place that uses a formalized testing process.

Test automation involves automating a manual process already in place that uses a formalized testing process.

Benefits of Automation

Reliable: Tests perform precisely the same operations each time they are run, thereby eliminating human error.

Repeatable: You can test how the software reacts under repeated execution of the same operations.

Programmable: You can program sophisticated tests that bring out hidden information from the application.

Comprehensive: You can build a suite of tests that covers every feature in your application.

Reusable: You can reuse tests on different versions of an application, even if the user interfaces changes.

Better Quality Software: Because you can run more tests in less time with fewer resources

Fast: Automated Tools run tests significantly faster than human users.

Cost Reduction: As the number of resources for regression test are reduced.

Other: Test without any human interaction

Why Automation is required?

Ø Reducing test time and resources

Ø Consistent Test Procedures

Ø Ensures process repeatability and resource independence

Ø Eliminates errors of manual testing

Ø Improves efficiency of testing

Ø Reducing testing costs

Ø Gives consistent and accurate results

When to automate?

Ø Regression testing

Ø Data-driven testing

Ø The Application under manual test is stable

Ø Application which has long runs

Regression Testing: Regression test suite is the best candidate for automation. If testing only needs for short period projects, it should be done manually. If the test suite needs to be run for a long time, regularly for every iteration, build and after bug fixing, then it should be automated. Always automate Smoke test cases then Sanity test cases and then regression.

Data-driven testing: Single test to verify multiple data like want to test application with various users.

The Application under manual test is stable: We cannot automate application which is unstable i.e when the functionality of application keeps on changing.

Long Run Projects: Long run projects are good to go with automation. Automating short duration project does not make sense. I personally go for automation for those projects whose duration is more than 6 months.

When to NOT Automate?

Ø Functionality of the application changes frequently

Ø Project doesn’t have enough time

Ø Test with unknown results cannot be automated

Automation & Mind

Automation testing started. What are all in my (your) mind?

· Is application stable?

· Need to analyze the requirement.

· What are the pages/modules involved.

· What manipulation happens to the data?

· What kind of framework need to be implemented?

· Need to improve in-depth knowledge of the domain.

· Will my framework applicable for web application?

· What are the field validations?

· Where is information stored in the database?

· Questions related to object handling in the application.

· Are the business rules that manage the process?