Take the 2-minute tour ×
Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It's 100% free, no registration required.

We have developed a project, QA already verify the project and now its ok to air. but i am still wondering about expected bugs.

So my question is how many testing technique is there to certify a product?

share|improve this question
1  
You have not mentioned what kind of application it is?. What techniques you have followed so far. Only then you will get what you actually expect. –  Balaji Kothandaraman Aug 18 '11 at 11:15
    
Good, but I already got an answer. –  pir abdul wakeel Aug 18 '11 at 16:56
add comment

2 Answers

up vote 9 down vote accepted

This is a difficult question, and it really depends on what you want to acheive and what you already have in place. Generating tests can be a long and labourious, and this goes severalfold for automated tests.

So the question "how many types of testing should I perform" has the answer "it depends on what you're trying to acheive and how much time/money you have to do it". The question "how many testing techniques are there to certify a product" depends on what your project counts as "certified". You cannot fully and exhaustively test the average project.

It's also hard to see what will apply to your project. For example there is Static testing (looking at the code) and Dynamic testing (checking the code at runtime). There's white box testing, black box testing and grey box testing. There is functional and non-functional testing. User acceptance, GUI, security, sanity and smoke, automated and manual, performance and load, stability, and various other types or mechanisms of testing.

It may be sensible to trust QA's decisions on this, just let them know what you want to achieve: find more bugs, fewer regression bugs missed, increase in coverage/finding more bugs in certain areas of the project, finding more critical bugs earlier, quicker repair of the testing architecture after code changes (maintainability/speed). Look at what comes back from your Beta testing, or at least what feedback you get from the users when you launch.

One more thing: testing is probably something you should be doing throughout the cycle. It's not going to be easy to suddenly ask for a system to be tested when it's ready to air, unless you intend to continue testing after the release.

share|improve this answer
    
but you know as i qa manager, i have to certify that the product is ok to live. –  pir abdul wakeel Jun 23 '11 at 8:44
4  
You do, but you can't produce a sensibly complex project with no bugs. You can only aim for the highest quality you can acheieve with your time and budget. Saying "ok" to the project going live is basically saying something like "this project is in such a state that the critical areas of the system work as expected, there are no bugs that prevent the core use by the users, and all other bugs are as low as we can get them" –  kinofrost Jun 23 '11 at 9:00
1  
Some examples of "done" for an agile environment are here: sqa.stackexchange.com/q/1108/729 –  kinofrost Jun 23 '11 at 9:01
    
really good answer kinofrost. +1 and Mark answer. how can i can appreciate your answer. –  pir abdul wakeel Jun 23 '11 at 10:08
    
Most welcome. I live to give. –  kinofrost Jun 23 '11 at 10:32
add comment

Abdul, I suspect you are looking for a cookie-cutter approach to satisfy some desired level of confidence. Such a cookie-cutter doesn't exist.

Techniques are systematic approaches based on heuristics to help solve very specific types of problems within a given context.

"Certifying" a product, or "signing off" from a testing perspecive is either an implicit or explicit contract between the test team and management (or employer) that the product has met or exceeded stated criteria.

The test team will use various techniques, approaches, and methods to evaluate and provide feedback against the stated criteria, but it is analysis of the information that is provided by the testing that helps you as manager make the final decision to 'certify' the product or provide compelling evidence to the decision-makers why the product is not ready to go live.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.