Hi,Can anybody pls let me know "what is the actual need for
test strategy when there is test Plan?"Whay is test plan
needed?
Answers were Sorted based on User's Feedback
Answer / bindu laxminarayan
Test Strategy is a high level document that contains the
information about the test approach, organisations mission.
All the information are completely at the organisational
level.
Test plan is a detailed document that contains the details
of the product such as what to test, when to test, how to
test etc. Test plan can single for the whole project or it
can also be written for every test level(component
testing/itegration testing/system testing) etc.
Is This Answer Correct ? | 4 Yes | 0 No |
Answer / manu
Test strategy: is used to decide which testing techniques
(Whitebox or blackbox testing ) will be used on proposed
application.
Test plan: is document that contains introduction,
assumption, list of features to be tested, list of features
is not to be tested,list of test cases, delivariables,
risk, resource, time, budget etc.
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / kiran goud
Test Strategy: is a document defines the process of entire project.
Test Plan: is a detail document for the particular release not for the entire project.
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / akshay
Test Strategy is high level doccument contains test
efforts,Test Configurational items,which tool emplyed,entry
and exit cretaria for testing etc.Done by Test Manager
Test plan is concern to that project only contain Objective
of testing,Assumptions,Risk Analysis,Test Tools,Scope,Test
Scedule,Roles n Responssiblities etc.
So that both r important becoz Test strategy represents How
Testing activities take place n Test plan represents How to
perform testing,By Whom,How,When to start ?
Is This Answer Correct ? | 0 Yes | 2 No |
Answer / chitti
Test strategy defines required test approach for the
project,it is company level terms.
Tst plan intructs u what to test ,who test ,when testing to
stop,what techniques follow to design test cases.which
contains complete informations abut automation tool.
Is This Answer Correct ? | 0 Yes | 3 No |
explain the Compatibility testing
Defect Migration "Defect Migration" means that error is early project documents lead to errors in later documents. For example, an incorrect requirement leads to an incorrect set of speacifications, which leads to design errors, which leads to coding errors, which lead to failures when we test against user expectations. a. How will you prevent Defect Migration? b. Why do you think preventing Defect Migration is important?
any one can explain error guessing..?it depends on validation or functional testing? give one example ..?
In front end if you enter one record it will be inserted in to 20 tables in back end.so How you are going to test in Manually whether data is going properly in to concern data tables or not? Is there any better solution to do that instead of opening the table and checking individually?
How we will assign the severity n priority levels to the bug?
What if the software is so buggy it can't really be tested at all?
What is the difference between the test case and a test script
How will u decide test data to see that evey feature is thoroughly tested
in google home page here when i click on images it displays images page and when i click on map it displays maps & when i click on youtube it display youtube page what type of testing is this?
What if there isn't enough time for thorough testing?
can som1 can tell me that can two or more tester can be given the same project for testing such as unit, regression,UIT,retesting. suppose the project has 10 modules so can all the tester will be asine to write the test cases for same or for differt modules? and in one project how many testers of the same level can participate? plz answer it fast. txs in advance and in which phase we will do the retesting in stlc
What is the scope of manual testing?Please let me know because I want my carrer as a tester.