Please reply me.
What is a full procedure to carry out testing.
We always say that testing is started early in the Software development life cycle but can anyone please tell me the full procedure to do the same.
I will explain it properly:
1) Now i have requirements(SRS), what will be the QA job, how to carry out testing?
2) Next is Functional Design specification, what will be the QA job, how to carry out testing?
3) Next Internal Design specification, what will be the QA job, how to carry out testing?
4) Next is Coding?, what will be the QA job, how to carry out testing?
Rest i know....
also please tell me When can we start writing test cases?
Can we start writing test cases when we have all documentation or we should start writing test cases only when build or version of the software is ready because there is one field in test cases where we have to enter what is actually happening.
And if there is web based application then is there any need to know all hardware or networking details to the tester, because in one company questions was asked to me that which Router do you use, what is IIS, what is install guide, Server details etc.......?
please , please , please , please clear my doubts.
First, this isn't the best place to post the question, as it isn't web-specific. Part of this is relevant to the Requirements and Design forum, and the rest might be more appropriate in the General forum.
Having said that, you would be looking at the requirements to verify that they are complete, non-contradictory, and testable.
As far as the internal design and code, it should be the responsibility of the dev team to make sure these are being done correctly. I suppose you could look to see that all areas have been considered in the design, and that any company standards are followed. If you wanted to review code, you might be looking to see that code is commented and not too difficult to read (though again this should be a dev task.)