1. What is Regression Testing? When we do Regression Testing? and Why Regression Testing?
Answer: Re-execution of same test cases on different builds or releases to ensure changes made has not introduced a defect in the unchanged features of the application.
2. What is difference Re-testing Vs Regression Testing?
Answer:
Re-Testing: After a defect is detected and fixed, the software should be retested to confirm that the original defect has been successfully removed. This is called Confirmation Testing or Re-Testing.
Regression testing: Testing your software application when it undergoes a code change to ensure that the new code has not affected other parts of the software.
3. What is Integration Testing?
Answer: Testing the data-flow between 2 features or 2 modules is called as integration testing. Once all the individual units are created and tested, we start combining those “Unit Tested” modules and start doing the integrated testing. So the meaning of Integration testing is quite straightforward- Integrate/combine the unit tested module one by one and test the behaviour as a combined unit.
The main function or goal of Integration testing is to test the interfaces between the units/modules.
4. What is Approaches/Methodologies/Strategies of Integration Testing?
Answer: The Software Industry uses variety of strategies to execute Integration testing , viz. Big Bang Approach : Incremental Approach: which is further divided into Top Down Approach and Bottom Up Approach, Sandwich Approach – Combination of Top Down and Bottom Up.
5. What is Traceability Matrix and Explain RTM and Why RTM?
Answer: Requirement Traceability Matrix or RTM is a document that maps and traces user requirement with test cases. The main purpose of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality should miss while doing Software testing.
5 Top Benefits of Using a Traceability Matrix
1. Save Time Now — and Later
2. Ensure Requirements Are Implemented
3. Get ‘Free’ Requirement Verification
4. Improve Change Management
5. Provide Evidence of Risk Mitigation
6. What is Entry and Exit Criteria?
Answer:
Entry criterion is used to determine when a given test activity should start. It also includes the beginning of a level of testing, when test design or when test execution is ready to start.
Examples for Entry Criterion:
Verify if the Test environment is available and ready for use.
Verify if test tools installed in the environment are ready for use.
Verify if Testable code is available.
Verify if Test Data is available and validated for correctness of Data.
Exit criterion is used to determine whether a given test activity has been completed or NOT. Exit criteria can be defined for all of the test activities right from planning, specification and execution. Exit criterion should be part of test plan and decided in the planning stage.
Examples of Exit Criteria:
Verify if All tests planned have been run.
Verify if the level of requirement coverage has been met.
Verify if there are NO Critical or high severity defects that are left outstanding.
Verify if all high risk areas are completely tested.
Verify if software development activities are completed within the projected cost.
Verify if software development activities are completed within the projected timelines.
7. What is System Testing?
Answer: System testing is the type of testing to check the behavior of a complete and fully integrated software product based on the software requirements specification (SRS) document. The main focus of this testing is to evaluate Business / Functional / End-user requirements. It focuses on testing the system as a whole.
8. What do you verify in System Testing ?
Answer: System Testing enables us to test, validate and verify both the Application Architecture and Business requirements.
9. What is Defect Life Cycle?
Defect life cycle, also known as Bug Life cycle is the journey of a defect cycle, which a defect goes through during its lifetime. It varies from organization to organization and also from project to project as it is governed by the software testing process and also depends upon the tools used.
10. What is difference b/w Defect and Bug and Error?
Defect: The variation between the actual results and expected results is known as defect. If a developer finds an issue and corrects it by himself in the development phase then it’s called a defect.
Bug: If testers find any mismatch in the application/system in testing phase then they call it as Bug.
Error: We can’t compile or run a program due to coding mistake in a program. If a developer unable to successfully compile or run a program then they call it as an error.
11. What is Smoke Testing and Sanity Testing and why we do and when we do? Difference ?
Smoke Testing is a kind of Software Testing performed after software build to ascertain that the critical functionalities of the program is working fine. It is executed “before” any detailed functional or regression tests are executed on the software build. The purpose is to reject a badly broken application, so that the QA team does not waste time installing and testing the software application.
In Smoke Testing, the test cases chosen cover the most important functionality or component of the system. The objective is not to perform exhaustive testing, but to verify that the critical functionalities of the system is working fine.
For Example a typical smoke test would be – Verify that the application launches successfully, Check that the GUI is responsive … etc.
Sanity testing is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.
The objective is “not” to verify thoroughly the new functionality, but to determine that the developer has applied some rationality (sanity) while producing the software. For instance, if your scientific calculator gives the result of 2 + 2 =5! Then, there is no point testing the advanced functionalities like sin 30 + cos 50.
Which methodology are you following?Explain.
Explain Agile Testing Methodology?
What is Scrum Testing?
What is White Box Testing?
What is Static Testing?
What is Performance Testing ? Explain j-meter?
What is Load Testing?
What is Stress Testing? Why Stress Testing? How to do Stress Testing ?
What is Volume Testing ? Why we do Volume Testing and how to do Volume Testing?
What is Scalability Testing? Why we do Scalability Testing and How to do Scalability Testing?
What is difference b/w Test Plan V/s Test Strategy?
What is difference Static Vs Dynamic Testing ?
What is SDLC and STLC?
What is Unit Testing and why we do unit Testing and when we do Unit Testing? and this black testing or white testing?
Non – Functional Testing?Can u explain All Non – Functional Testing have u done Non – Functional Testing if u done explain which tool u have used?
What is Test Scenario ?When we create Non – Functional Testing?
What is Test Case and why we write test case ?Can u explain your Template of test Case?
What is difference of Test Case and Test Scenario?
What is the Test technique?
Can u explain Equivalence Partitioning & Boundary Value Analysis?
What is Decision Table Testing?
What is Test Plan ? Why Test Plan and who is creating test plan and Explain Template of Test Plan?
What is Defects?
What is difference Quality Assurance Vs Quality Control?
What is difference b/w Verification v/s Validation in a Software Testing?
What is difference b/w Positive Vs Negative Testing?
What is Security Testing and why we do Security Testing and have u do Security Testing please explain how to do Security Testing?
What is End to End Testing why we do End to End Testing and when we do End to End Testing can u give me real example of End to End Testing?
Explain Exploratory Testing?
Explain Adhoc Testing ?
What is Pilot Testing?
What is Endurance Testing?
What is Grey Box Testing?
What stub and Driver?
What is Beta Testing?
What is Alpha Testing?
What is V-model?
What is waterfall model?
Which tool u are u using for raising for bug? Can u explain all navigation Step?