Testing Interview Questions

Sub Category
Questions
Answers
Last Updated
5
35
Mar 1st, 2017
116
2470
Apr 21st, 2018
333
4374
Sep 8th, 2022
60
737
Oct 27th, 2017
96
593
Sep 27th, 2017
235
2158
Jan 24th, 2019
129
974
Jun 16th, 2019
144
659
Aug 18th, 2017
17
120
Sep 27th, 2017
353
3233
Sep 8th, 2022
161
1149
Jan 9th, 2024
336
3125
Dec 1st, 2022
219
2921
Oct 31st, 2021
291
1719
Nov 2nd, 2019
535
3151
Sep 9th, 2022
118
1046
Nov 7th, 2020
31
138
Mar 14th, 2012

Showing Questions 21 - 24 of 24 Questions
First | Prev | Next | Last Page
Sort by: 
 | 
Jump to Page:
  •  

    Prevent Defects

    How can the Testing Organization help prevent defects from occurring?

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Nov 20th, 2009


    The earlier QA?gets involved in the?software?development process, and the?greater their presence in this process, the more they will help prevent defects.?

    QA can review software design documents (cross-functional peer reviews)?before software engineers begin developing their code.? QA can maintain its presence and continue to offer feedback throughout the development process until the initial release of the program to test.??

    QA will not prevent defects from occurring, but can minimize the quantity and severity of defects by:
    1) Fully understanding the scope of the software development project,
    2) Getting involved at the earliest possible stage in the development cycle,
    3) Reviewing the project plan for development and offering feedback, and
    4) Maintaining a presence in the development process before the first release to test.

    kurtz182

    • Nov 20th, 2009

    The earlier QA?gets involved in the?software?development process, and the?greater their presence in this process, the more they will help prevent defects.? QA can review software design documents...

  •  

    Testing Effort Estimation

    How to estimate testing effort following two cases i.e. 1. If Client having high level requirement only. Ex:100 high level requirement2. If client having prototype of the application only.3. If Client having usecases only.4. If client does have any req or usecases.

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Nov 8th, 2009


    I'm not sure I fully understand the question, but I will take a stab at this:

    In our group, the testing effort is generally considered to be 30 percent of the total development effort in terms of resources when all of the deliverables are properly and thoroughly provided to the test team.   These deliverables include requirements and specifications.

    "Requirements" refers to the business requirements of the program
    "Specifications" refers to the technical specifications of the program

    In our group, it is a bonus if we receive usecases.  Typically, this isn't necessary when a complete and thorough listing of requirements have been provided.

    1.  If the client only has the high level requirements, then it depends on how "high" the requirements truly are.  If the requirements are so high that all of the necessary test cases can not be reasonably produced with the information given, then extra effort will be needed to query for more complete requirements.  If testers must ask specific questions because details are not fully explained in the requirements, this will necessarily incur an increase in test time and resources.

    Likewise, the test team has not been given technical specifications for the program.  This will incur even more test time and resources when questions are raised such as, "What is the maximum number of characters users can enter in this text box?" or "Are users required to enter a phone number in any particular format?"   

    In scenario 1, the testing effort estimation is much greater than 30 percent and its specific value depends on information that has not been divulged.

    2.  If the client only has a prototype, the test team will make it clear that it can not verify whether the program meets company business needs because there are no requirements.  Without requirements, the test team can only ensure that the program is stable and user-friendly.  The test team may push back and let project manager/marketing/engineering know that it does not recommend an appreciable amount of test effort be applied to the project until requirements are provided.  If the test team is compelled to devote a full test run on the project, then it must be made clear that test will not endorse (sign off) on the project and will have to test the program again when the requirements are furnished to the test team. This being the case, significantly more test time and resources will need to be applied to the project.  

    As we saw earlier, even more test time and effort will be needed when questions arise due to the lack of technical specifications.

    In scenario 2, the testing effort estimation is much greater than 30 percent and its specific value depends on information that has not been divulged.

    3.  If the client furnishes usecases, and if the usecases were based on business requirements, then test will need to verify whether all of the requirements were covered in the usecases.  If not, then more test time and effort will be needed to ask the appropriate questions to fill the gap of missing requirements.  If the usecases cover all the requirements, and if we can get project manager/marketing/engineering to confirm and sign off on this, then test can begin authoring test cases based on the use cases. 

    Yet, as we saw earlier, more test time and effort will be needed when questions arise due to the lack of technical specifications.

    In scenario 3, the testing effort estimation is greater than 30 percent but less than scenarios 1 and 2.  Still, its specific value depends on information that has not been divulged. 

    4. If the client provides the requirements and usecases, then we are still missing the technical specifications.  Yet, this scenario gets us closest to the test team's resources being 30 percent of total development cost.  Nevertheless, it is still over 30 percent.

  •  

    Test Design

    What is Test Design? Is it preparing the test documents or is it test identification? If the "Test Design" refers to only test identification and "Test Execution" refers to validation, then where should we fit "test document preparation"

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Dec 30th, 2009


    Test Design includes all of the steps leading up to Test Execution.  The preparation of test documents and the identification of tests are performed simultaneously.  Consequently, test document preparation is included in Test Design. 

    kurtz182

    • Dec 30th, 2009

    Test Design includes all of the steps leading up to Test Execution.  The preparation of test documents and the identification of tests are performed simultaneously.  Consequently, test document preparation is included in Test Design. 

  •  

    Handle Changes Before Ship Date

    How would you deal with changes being made a week or so before the ship date?

    Star Read Best Answer

    Editorial / Best Answer

    kurtz182  

    • Member Since Nov-2009 | Dec 28th, 2009


    I would determine the feasibility of meeting the ship date by evaluating the:

    1) necessity of the change; [ why do we need it? ]

    2) urgency of the change; [ can we defer it? ]

    3) complexity of the change; [ how much time and effort will be required to test it? ]

    4) risks involved with not including the change; [ what happens if we don't do it? ]

    5) additional resources required to test the change [do I have the resources? ]

    Then I would either rally the resources to test the change or I would deliver a (hopefully compelling) case against releasing on the target ship date based on my evaluations. 

Showing Questions 21 - 24 of 24 Questions
First | Prev | Next | Last Page
Sort by: 
 | 
Jump to Page: