Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / deep
If you are writing test case then you need input data for
any kind of test. Tester may provide this input data at the
time of executing the test cases or application may pick
the required input data from the predefined data locations.
Generally testers call it as testbed preparation. In
testbed all software and hardware requirements are set
using the predefined data values.
Tester can’t justify any bug saying that test data was not
available or was incomplete. It’s every testers
responsibility to create his/her own test data according to
testing needs. Don’t even rely on the test data created by
other tester or standard production test data, which might
not have been updated for months! Always create fresh set
of your own test data according to your test needs.
| Is This Answer Correct ? | 2 Yes | 0 No |
Post New Answer View All Answers
You may undergone many projects. Do all the projects match up with customer’s expectations?
What can you tell about the project if during testing you found 80 bugs in it
Tell me a critical defect in which your Client,PM,PL appreciate on you
What is software configuration management?
what is TAS language which is used as a language for some projects/
What is difference between V-Model and Agile Model?
What is the difference between pilot and beta testing?
Information about Automated Software Installer
What are the standard you follow in your company to prepare test plan document? Content is same in every standard or not. Also is there any document to read about the testing standards? Thanks in advance for giving me the answer.
Can you explain exploratory testing?
Have you ever completely tested any part of a product? How?
Which testing model is best as per your understanding, and why?
HI FRNDS, I HAVE 2.5 years OF exp In Manual Testing,Plz let me know if thr r any oppurtunities in any company in Bangalore ID:dsnithi@gmail.com Thanks in Advance
i need some objective type papers for my certification
Scenario-based testing Option 1 concentrates on actor and software interaction Option 2 misses errors in specifications Option 3 misses errors in subsystem interactions Option 4 Both 1 abd 2
