What Tester should do after getting Requirement Doc?
Answers were Sorted based on User's Feedback
Answer / saran
First we know about clear requirement function, after they
will go and write a test cases
| Is This Answer Correct ? | 33 Yes | 0 No |
Answer / amit verma
After getting Requirement doc. like FRS/BRS, we take
understanding for the same & discuss it with TL(if
necessary).
Then v vl start to create Test Scenarios and Test Cases
based on the understanding of Req. doc.
| Is This Answer Correct ? | 17 Yes | 0 No |
Answer / n@n!
->prepare test cases after understanding the requirement
document
->waiting for application from developers for testing.
| Is This Answer Correct ? | 9 Yes | 1 No |
Answer / ramsha
1) First we should know the level of testing (ex: in safety
Critical systems follow DO-178B Level A to D or SIL Level 1
to 5).
2) Clearly understand the testing.
3) As mentioned in the SVP follow testing process
4) Should know Its a delta (partial) or full testing
5) Based on testing tool develop test script on the
specified language/script
6) Design test cases
7) List out assumption and constraints
8) develop test scripts
9) execute and collect the report
10) Document the result, justify the valid failure otherwise
report it.
| Is This Answer Correct ? | 7 Yes | 0 No |
Answer / john
After getting th BRS & SRS, will discuss the same with
product/stake holders ( Dev team/ UED team/etc) to get
clarify the question on these spec's.Once this is done will
write TEST PLAN. Based on it we will write tc's
accordingly..
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / sandeep
after getting requirements doc first we have to analyze the
requirements and understand the functionalities of the
requirements like which has high priority means which
perform major operation in the application then write test
cases.
| Is This Answer Correct ? | 3 Yes | 0 No |
When a tester recieves a req doc he should first of all
understand the req doc completely. then
1) He should review that document look for some missing
functionalities in the doc.
2)Look for some inconsistancy in the doc. Check wheather
all the req are consistsant or not.
3)Check weather requirment are complete or not.
4)Check all the req in the doc are testable or not.
5)Do some research about the customer, and see if the req
when built address the customer problems.
6)If req is for a mission critical systems(Military) See
all the military standards and guidelines are followed or
not.
After doing this all
Tester should start identifying the test conditions once
all test conditions are identified. Tester should start
desinging test cases that will verify these conditions.
Prepare a RTM and see if all the req are covered by the
test cases.
This is how it should go
Correct me if i am wrong
| Is This Answer Correct ? | 4 Yes | 2 No |
Answer / abha
After getting requirements doc, depending upon the type of
application master plan or test plan should be made.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / nithu
After getting the Requirement document first test engineer identifying,understanding and documenting.He will prepare test cases.
| Is This Answer Correct ? | 1 Yes | 0 No |
After getting requirement we should go thru it. we refer to
the Mock up & try to find out any Gap analysis in the req
doc.if any discrepancies found, we should contact the stake
holder of that doc. If it is confirmed as a Gap then we
should follow the loop & maintain a log/record until a new
requirement version is delivered to us. Then STLC follows.
Please correct me if I am wrong.
Thanks,
Bibhu
| Is This Answer Correct ? | 0 Yes | 0 No |
Which model should we use and under what scenarios?
Can anyone give me the example of High Priority and Low severity defect. Please dont give me answers like Spelling mistakes or logo missing something like that. Give me some real time example from your application. Please ignore the earline question which i have posted.Thanks in Advance.
What did you achieve being a tester
what is the entry criteria and exit criteria of integration testing?
1. fault based testing is reversed of which testing? option.1 conventional software testing Option 2Operations and classes that are critical or suspect Option 3 Use-case validation Option 4White-box testing of operator algorithms 2. Testing OO class operations is made more difficult by Option 1 Encapsulation Option 2 Inheritance Option 3 Polymorphism Option 4 Both Inheritance and Polymorphism 3. Which of these techniques is not useful for partition testing at the class level Option 1 attribute-based partitioning Option 2 category-based partitioning Option 3 equivalence class partitioning Option 4 state-based partitioning 4.Client/server architectures cannot be properly tested because network load is highly variable. Option 1 true Option 2 false 5. Real-time applications add a new and potentially difficult element to the testing mix Option 1 performance Option 2 reliability Option 3 security Option 4 time 6.Which one is not key term used in internal control and security Option 1 Threat Option 2 Risk Control Option 3 Vulnerability Option 4 Exposure 7.Acceptance testing occurs only at the end point of the development process; it should be an ongoing activity that test both interim and final products. Option 1 true Option 2 false 8.Static testing requires...? Option 1 Binaries Option 2 Source code Option 3 Product Option 4 Executables 9.etesting is testing the application with multiple sets of data is called retesting Option 1 true Option 2 false
After which phase you are performing UAT?
what is meant by Inspections? what arewalkthrough?
What are the meetings conducted your company
What is the test case?
Can a Tester test any application without Specifications/Requirements?
Who will close the bug and how it is closed..........?
11 Answers HP, IBM,
in database testing, which are the things u used?