Pratheesh

• Nov 5th, 2012

Retesting is testing again after fixing a defect. we are testing the particular module only what we have changed and testing the test case in the same build. Regression testing is the testing the syst...

Sandhya

• Jun 21st, 2012

Retesting: Testing the functionality of the application frequently to ensure that the changes made in particular module is working properly/not. Regression: Testing the entire functionality of the app...

Answer Question  Select Best Answer

Neha Sharma

• Nov 28th, 2015

Verification is a process to check whether the software is according to its specification, for what purpose it is designed, whether performing that way or not whereas validation is a process to check whether is software or product is according to the customer needs or not.

srikanth yeluri

• Oct 20th, 2015

Verification: It is something like verifying the documents Ex:- SRS, DRS, ADD. It is a static testing or we can say walk through reviews

Validation: Validating the test results after starting the executing.

Answer Question  Select Best Answer

Read Best Answer

Editorial / Best Answer

rajanee  

 Profile Answers by rajanee Questions by rajanee

• Member Since Jan-2006 | Jan 6th, 2006

---

 Black Box and White Box are testing types and not tetsing techniques.

Testing techniques are as follows:-

The most popular Black box testing techniques are:-

• Equivalence Partitioning.
• Boundary Value Analysis.
• Cause-Effect Graphing.
• Error-Guessing.

The White-Box testing techniques are: -

• Statement coverage
• Decision coverage
• Condition coverage         
• Decision-condition coverage
• Multiple condition coverage
• Basis Path Testing
• Loop testing
• Data flow testing

Aakash Bhavsar

• Aug 7th, 2017

Follow this: Methods of testing: 1) Black box testing 2) White box testing 3) Gray box testing 1) Black box testing techniques: Equivalence class partitioning, Boundary value analysis, Cause effec...

Mayuri Padhye

• Jul 19th, 2017

As black box and white box testing are the types of testing then what are the techniques of testing

Improve Answer

selim

• Sep 14th, 2023

Yes, generally that is how it executed where QA/Tester always assign the priority proportional to severity which has no meaning at all. In the end, dev should decide the priority. Tester assigning the priority has no function at all which makes it a slightly wrong application

bhuvan

• Jun 24th, 2014

Severity will be decided by test end and priority will be decided by dev end in triage call

Answer Question  Select Best Answer

Smoke testing is after build releasing we will test high level functionalities working or not. Sanity testing is we will test all functionalities working properly or not.

Anonymous

• Dec 15th, 2014

Please make sure you know what actually it is.. Don't misguide.. sanity testing is like a narrow regression testing, usually done after a builds are deployed (After bug fixes) to make sure functionality is still correct.

Ramasubbu

• Aug 3rd, 2014

Smoke testing: Testing the critical functionality of the application using high level test cases and check whether the application is ready for further testing(General health checkup) Sanity Testing:...

Answer Question  Select Best Answer

ciprian1

 Profile Answers by ciprian1 Questions by ciprian1

• Jun 2nd, 2010

Testing is the verification of the customer requirments and black box testing are test that only knows the input and the output of the test, but not knowing the internal mechanism of the test.

graleh

 Profile Answers by graleh Questions by graleh

• Feb 2nd, 2010

This is a big area with a lot of methods and esp. if you want if from the basics.. The best thing is to attend a course or read a book about it. I recommend "Foundations of Software Testing" by Dorothy Graham.

Answer Question  Select Best Answer

Can any one answer to this question

Anant Chaudhary

• Mar 14th, 2013

There are 2 goals:

1)To improve the quality of product by finding hidden defects.
2)By testing ensure that all customer requirements are full fill in the product.

Radha

• Jan 17th, 2013

The two primary goals of testing is 1. To make sure that we have covered all the requirement and functionality which is given by the client and the customer. 2. Most important of the Quality team i...

Answer Question  Select Best Answer

Could please anybody give me the good examples of:

High severity and Low priority
Low severity and High priority
Low severity and Low priority
High severity and High priority
Med severity and Med priority

.... in the terms of functionality.. and Please tell me who will give the priority.

Anjum khan

• Apr 28th, 2024

Severity :- impact of the defect on customer business. Priority:- importance of fixing that defect. High severity and High priority:- login functionality is not working properly . Because i...

shraddha

• Apr 4th, 2018

Logo issue would be high priority and low severity as its not affecting the functionality.

Answer Question  Select Best Answer

Munna

• Aug 26th, 2014

Severity describes the impact of the bug, where as Priority describes the importance and order the bug should be fixed.
Tester will use Severity for reporting a bug.

sandeep kumar

• Jun 14th, 2014

Both are used by the tester. Severity and priority are set depend upon the nature of defects. Ex:- If we are working on any project and after completion every thing was fine but there was a spelling...

Answer Question  Select Best Answer