vk1978

 Profile Answers by vk1978 Questions by vk1978

• Feb 19th, 2009

 

If you have incomplete requirements, then you have to do Exploratory Testing, where you need to communicate with business analyst,?seniors,?developers, team mates for better understanding of?the functionality?and also while research on the AUT so that you can understanding the flow and functionality.

G.D.S.Prasad

 Profile Answers by G.D.S.Prasad Questions by G.D.S.Prasad

• Mar 11th, 2009

 

If the requirements are incomplete / Unclear it is the tester's responsibility to get the details from various sources like BA, Designers, Developers etc. You cannot proceed further unless you are clear with requirements.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Mar 19th, 2009

 

If the requirements are unclear then I can follow the below steps.

1. First of all,
I will prepare the review report with all clarifications/doubts about the unclear requirements.
2. Next, sent to the concerned persons like BA if available and get the required information.
3. If you (tester) have a direct contact with client then ask him directly via emails or phone, in my project we are using a common tool, we can post all our
doubts there and concerned persons will respond to them.

sudhakar.s1206

 Profile Answers by sudhakar.s1206 

• Apr 17th, 2009

 

The first thing needs to be done is the Requirement analysis. The testing process should be started if and only if the requirement is freezed. Infact the estimation of testing will vary depends on the requirement updations and clarifications.

shakilag

 Profile Answers by shakilag 

• Jun 23rd, 2009

 

If requirements are unavailable or incomplete it makes a difficult task to go about with test case design. In such a case the following can help:

1) Arrange a session on project requirements with BA/SA to fill in the incomplete gaps.

2) Understand the requirements from them. Draw use cases or high level scenarios and get it reviewed from BA to check that you are on a right track.

3) From these uses cases/ high level scenarios, come up with test cases and again get it reviewed so that you rework on the same and your final set of test cases are ready.

4) If possible even prioritize the test cases in order of each requirement's criticality which will help in effective  test execution.

 

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Aug 31st, 2009

 

If the Requirement is in completed, then we can do Exploratory Testing. While executing the Test, what ever queries arised should be notable and send to the concern for answer. That should be clear and understandable.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 3rd, 2009

 

When requirements are incomplete or unclear, it is a tester's responsiblility to address this issue with business analyst, project manager, developers, or other stakeholders responsible for making changes and ensure that the gap is filled before test execution begins. 

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 4th, 2009

 

If I ran across an incomplete requirement during my requirements review, I would
1) inform the Business Analyst (person in the organization responsible for preparing requirements) and set up a time to meet with this person to discuss the requirement gap.
2) discuss the nature of the incomplete requirement in the meeting, making sure the Business Analyst fully understands the requirement gap so s/he can revise the requirement and fill the gap.
3) author test case(s) that accounts for the incomplete requirement.
4) have the Business Analyst review the new test case(s) to ensure they are accurate and thorough.
4) Map the new requirement(s) to my new test case(s).
5) Prioritize my new test case(s).