We are working on a web application project.But there are such many uncleared requirement: business logic, usability...
I asked developers to find out the resolution and fix them, but I got some reply like: 'we have many things need to do, some features still not implemented, you could overlook them...anyway, there are no definition in the SRS.'
I am really confused for what should we concentrate on? The product quality or the customer requirement?
What shall we do if the customer also not care/clear of these detailed things?
Anybody here has similar experience?
Willing to talk to CSQA, since I am preparing for that [img]/images/graemlins/smile.gif[/img]
Question - Why are you asking developers about the requirements.
Anyway in your situation what I would do is to try an essentialise the requirements i.e distill from the documented requirement, the bare essentials (devoid of technological implementation) and work to that. As the client refines his/her requirements, so you can build on your essentialised model of them.
GUI automation is GUI automation. It is not testing.
In our shop, we write QA plan and distribute this plan to team members. Team member includes:
- Project manager
- Technical Team lead
- Product Manager
- QA Director
- Configuration Engineer
Each member perform specific task which is defined in QA plan. Tester/QA Person goes throgh every phase and validates QA related tasks. For Example:
At Requirement phase, we validate following:
- Usecase/Functional Req complited?
- Non functional aspects in place?
- H/W and S/W acquisition defined?
- Store procedure defined?
- Stake holders signed off?
At Developement phase:
- Coding complited?
- Unit Testing complited?
- Code inspection complited? ( Documents, Code walkthrough, etc)
- Build created?
At Testing Environment:
- Test Plan signed off?
- Functional testing complited?
- UAT/Usability testing complited?
At Project Closure phase:
- Testing complited and signed off properly?
- Code migration complited?
- Peer review and communication complited?
All I am trying to say is that, we have pre-defined methodology/process and we follow that process and everyone is part the stake holders of that process. This help us a lot to perform our task at various stage of project development.
hope this Help.
Once the requirements have been fully defined and agreed, in the first instance you should concentrate on whther the delivered functionality meets the Requirement. What is the point of having a high quality chunk of functionality if it does not meet the Requirement and doesnt do what the user/customer wants?
Once you are satisfied that the delivery meets the requirement then concentrate your effort on the quality?