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.
Software QA Engineer-ARYAN InfoTech
Test-Driven Development is not a Testing........
Re: QA\'s responsibility
1. QA should verify the requirements prior to any coding. Test them for redundancy, accuracy, understandability, and preciseness.
2. QA should test the design specs for accuracy and clarity as based on the requirements.
3. QA should test the internal design specs for accuracy and clarity as based on the requirements.
4. If you are running an iterative approach, then Development will start dropping you pieces of the application as soon as they are ready and you will test them as best you can. If you are using a Waterfall approach, then you will not see anything until the app is almost complete. So you have plenty of time to write scripts.
QA does not write scripts, QC or testing does, and in a true QA the QA Architect does it, but they are usually part of QA. QC or testing can start writing scripts as soon as the requirements phase is completed.
The Web based answer is that all of the supporting information will be in the detailed specs. It should tell you which platforms, systems, browsers, etc. you will be responsible as well as the load requirements and the access times to be validated.
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~
Re: QA\'s responsibility
I would suggest two different approaches : verification (before coding) and validation (after coding, similar to test).
1/ on SRS QA can determine if there are any missing or ambiguous requirements. From use cases (if present in the SRS) you can determine areas to test, possible risks and possible test scenarios that will be filled out later on. By the way, you can determine quality requirements too, and you should look for ways to determine if a requirement is fulfilled or not (think metrics).
2/ Functional specs : same operations in order to ascertain that the specs become unambiguous and clear. From the functional specs you can design other test scenarios (sequence of test cases) and areas that have to be tested more thoroughly (for example because of their complexity).
3/ Internal design : same approach as for functional specs, except that you will now be able to design lower level test cases.
As QA, you will also have to ascertain at all times that the requirements are adequately covered by the design and by the tests, and that the design is adequately covered by the tests.
4/ QA can oversee the unit test execution, and test coverage. Whether the code is written after the test (test first programming), or before, and whether the unit tests execution is done by the developer or by testers, QA must make sure that the expected processes are executed and that the adequate metrics are provided (at least that is how it works here in the aerospace industry).
Creation of the test cases will be an iterative process as you will first start with high level test scenarios and finish with low level test cases.
As QA (Quality Assurance) you will have to provide reports on process quality and on product quality. Product quality is easy : its testing. Process quality is more ambiguous as you are working with people and they have to buy in to the planned process.
Applying QA to the web is similar, but you will have to determine quality requirements (type of browsers, routers, network bandwidth, response time, latency, ...) and ascertain that they are adequately covered by subsequent tests.
Hope this helps