Test Methodology, Scenario, and Test Case

Explain:

a.) Test Methodology

b.) Test Scenario

c.) Test Case

d.) Requirement traceability matrix

a.) Test Methodology
The testing methodology determines how an application will be tested and what will be tested. Examples of methodologies: waterfall, agile, etc.

b.) Test Scenario
Test scenario is a logical grouping of test cases and it mentions the sequence in which the test cases are to be executed.

c.) Test Case
A test case is a unit-level document describing the inputs, steps of execution, and the expected result of each test condition for every requirement from the BRD. Testers determine whether the application is working correctly or not based on the test case that is being executed. A test case is marked as “Pass” if the application works as expected and is marked as “Fail” if otherwise. Test cases also aid in generating test status metrics.

d.) Requirement traceability matrix
RTM is a matrix tying up requirements with the test cases. It is a way of making sure that every requirement has a corresponding test case that will be tested thereby ensuring complete requirements coverage.

Differentiate between smoke testing and sanity testing.

-Smoke testing verifies all areas of application; sanity testing verifies one or a few areas only.
-Smoke testing is done before accepting code for testing – Sanity testing is a subset of regression testing and is used whenever it is sufficient to prove that the application is working as per requirements.

What is STLC?

STLC is a Software test life cycle. It includes
1. Impact assessment: How much testing impact a new project has and how many levels of effort will be required.
2. Work allocation: Assigning resources to test the project
3. Requirements knowledge gaining: Understanding the BRD and SRS thoroughly
4. Test planning: Determining what will be the high-level test scenarios, what test data will be required, how to stage them, preparing the test plan, etc.
5. Writing test cases: Preparing test cases based on the understanding of the requirements and high-level test plan
6. Executing: Once the code is dropped, verifying the application based on the test cases.
7. Bug tracking: Raising defects and tracking them to closure
8. Traceability: Providing traceability documents to clients for passed test cases.
9. Sign off: Signing off the tested code once exit criteria are reached.

What would you do if you see functionality in the software which was not there in the requirements?

This scenario is called gold plating which is offering more functionality in the software than what was required by the client. In this situation, I would get in touch with the client contact and get their consensus about the new functionality. If they are happy with the new function, I will get it updated in the BRD and provide necessary updates to RTM, test cases, etc.

What is automation testing? Can automating a test improve the effectiveness of the test?

Test Automation is the execution of test cases with help of software like Win Runner, QTP, Selenium to compare the actual results with expected outcomes, by setting up preconditions or checkpoints. Automation testing is often used in regression testing than progression testing. It’s quite reliable and provides better results when used on the applications or systems which is quite stable. Otherwise, it would be laborious and time-consuming.
Yes, Automating a test makes the test process:
1. Fast
2. Reliable
3. Repeatable
4. Programmable
5. Reusable
6. Comprehensive

What are the various automation tools available in testing? How will you decide on a tool for test automation?