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

WEST

WEb Service & Testing

Techniques such as White, Grey and Black Box testing relates to traditional systems, which directly sync-up into Web Services deployments.

However, the following uniqueness of a Web Services deployments introduce exclusive testing challenges:

*) Web Services are fundamentally distributed and are platform and language doubter.
*) Web Services can be a sequence with dependencies on the other 3rd party Web Services that can change without notice.
*) Web Services ownership is shared across various stakeholders.

Software Testing || QA

Web Services || AWS

ABCDE of a Software Test Engineer

“ABCDE” of a Good Tester’s Quality;

• You Agree to the work/attend official calls apart from your office timings/working days.
• You are always Brisk on explaining the defects on tracking system.
• You are Conscious of your application’s business view and testing life cycle.
• You are Delighted doing multi-application testing.
• You are Ecstatic of your role in your project.

Open Quality Testing

:: OQT ::


<< Open Quality Testing >>

Being Practical = Being Human ?

1. I always wanted a Quality Analyst to be well-educated in scientific research.
2. They should have a great interest in Math and other related calculations.
3. They need to max-up with lateral thinking and have an agile mindset.
4. When they are busted off, the sound need to thunder other’s ears.
5. They should substantiate their individual characters before all expects to knowledge that out.

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

Testing is Hyped

• Good QA testers are worth their weight in gold.

• Unit testing finds certain errors; manual testing others; usability testing and code reviews still others.

• The peer pressure of knowing your code will be analyzed on providing higher quality.

• Another huge problem with developer tests is that they won’t tell you if your software sucks

• No single technique is effective at detecting all defects.

• Testers are a developer’s editor.