Interested to Buy Any Domain ? << Click Here >> for more details...
Overall what percentage of positive and negetive testcases
would you write?
- 5 Answers
- 12553 Views
- Accenture, I also Faced
- E-Mail Answers
Answer Posted / lakshmana rekha basu
50-50.
...but compared to positive testing in negative testing we
pump up More number of Different sets of data with an
intention of finding the bug.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
Explain storage testing?
what r the strategies & methodologies r u following in preperation of test cases based on usecase?
What n+1 testing is?
repeated testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software component:
What is emulator?
What is depth testing?
hi frens, i need ur help if nebody had worked or workin on online banking projects n online job portals ..frens cud u pls gimme the realtime examples for critical bugs, high severity n low priority bugs high severity n high priority bugs low severity n low priority bugs high severity n low priority bugs related to banking n job portal
What is coverage measurement?
Write a function Occurrences() in a language of your choice that takes in two strings. The first is a search string, and the second is a sentence. For example, running the function: Running Occurrences ("o", "Red Gate Software - Ingeniously Simple Tools") will output: Occurrences of 'o': 4 Occurrences ("at", "The cat sat on the mat") will output: Occurrences of 'at': 3 Sample Question 2: 2)Below is Notepad's File/Save dialog. a) If you were asked to test this dialog, how would you go about it? b) List various inputs you might place into the "File name" text field to test it.
What is a user interface?
What is bottom-up strategy?
26). how will know do written test cases are sufficient to validate application of functionality? 27). how will you prepare test data to validate input object? 28). explain defect status? 29). how will know whether the developer accepted you defects or not? 30). explain acceptance test? 31). explain when we stop testing? 32). explain scope of your project? 33). in which module you conducted testing? 34). explain defects which you found in that module? 35). if defect is not reproducible then what information you will provide to developer 36). if developer is not accepted your defect then what you will do?
What is path testing?
What is quality assurance (qa)?
What is software fault?
