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 |
what is Ping tests?
1...HOW TO RETRIEVE NUMBER FROM ALPHA NUMERIC VALUE? 2.. HOW TO CAPTURE A DYNAMIC VALUE IN WEB APPLICATION? 3.. HOW TO GET THE OUTPUT VALUE FROM ONE TRACTION AND USE THIS OUTPUT VALUE AS INPUT OF ANOTHER TRANSACTIONS? 4... HOW TO COUNT A WEB TABLE ROW? ... WHAT IS QC LIFE CYCLE? 6...WHAT IS IMPACT ANALYSIS? HOW TO DO IMPACT ANALYSIS IN PROJECT?
What r the risks involved in testing?
What is a show stopper?
You have been given 2 projects to test, what are the key factors you consider when prioritizing you work load?
How will u decide test data to see that evey feature is thoroughly tested
what is the diffrence b/w Sanity testing and smoke testing
write testcases for open dialogbox
define metrics? give me a brief detail about it?
This is the question related to Traceability Matrix. Say we have 10 requirements for a project. If one of the testing team member misses the 9th requirement. Then how can we justify the Traceability Matrix and what is the further action to be taken. Please advice.
Login screen with Username, Password input fields,remember me check box,sign in and reset button write Test Cases for GUI, Funcitonal, Negative, Usability and Security testing.
What is inter-operability?