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

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

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

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

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

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

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

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

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

some one Reply for this question

ravi

• Mar 7th, 2013

Test the application with invalid inputs is called negative testing.

Tanuja

• Mar 5th, 2013

It is a type of testing, one should have negative mind set and we should check all the functionalists and validations instead of providing positive inputs we should provide invalid inputs.

Answer Question  Select Best Answer

Read Best Answer

Editorial / Best Answer

AmitHam  

 Profile Answers by AmitHam Questions by AmitHam

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

---

1]High Severity And Low Priority----If  there is an application , if that application crashes after mulple use of any functionality (exa--save Button use 200 times then that application will crash)

Means High Severity because application chrashed but Low Priority because no need to debug right now you can debug it after some days.

2]High Priority And Low Severity---- If any Web site say "Yahoo" now if the logo of site "Yahoo" spell s "Yho"  ----Than Priority is high but severity is low.

Because it effect the name of site so important to do quick ---Priority

but it is not going to crash because of spell chage so severity low.

Amit Hambarde

Ajit.Rawat3

 Profile Answers by Ajit.Rawat3 Questions by Ajit.Rawat3

• Aug 30th, 2012

-> First of all make the clear understanding of severity and the priority of a bug. Severity:- How badly bug is effecting the functionality of an Application. Priority:- How quick we need to resolve ...

rohan.satpute

 Profile Answers by rohan.satpute Questions by rohan.satpute

• Jul 22nd, 2012

High Severity and Low Priority Bugs
- Issue supposes to be caused for Leap Year or Year end.
Low Severity and High Priority Bugs
- Issue such Spelling mistake on GUI Main Screen

Improve Answer

priyanka

• Aug 19th, 2018

Explanation is tooo good thank u soo much

Pradeep Singh

• Jul 1st, 2016

A mistake in coding is called ERROR, Error found by tester is called DEFECT, Defect accepted by developer is called BUG, If build does not meet requirements then it is FAILURE.

Answer Question  Select Best Answer

Gyanesh Gupta

• Oct 13th, 2014

Test Case: A software test case is a set of steps and expected results used to test an application. It is created from the software requirements. Well-written test cases can make the testing cycle smo...

pallavigajelli

 Profile Answers by pallavigajelli Questions by pallavigajelli

• Jul 16th, 2010

Use cases describe the system from the user's point of view A test case in software engineering is a set of conditions or variables under which a tester will determine whether an application or software system is working correctly or not.

Answer Question  Select Best Answer

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Nov 20th, 2009

The following are required to author test cases:1) Business Requirements Document (BRD)2) Technical Specification Document (TSD)The following are nice to have:1) Test Plan2) Architectural Diagram(s)  3) Work-flow Diagram(s)4) Approved Application Mock-ups

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Sep 14th, 2009

1.SRS2. Functional Document (FRS,BRS, etc..)3. Design Level documents(Use case, Design Screens)4. Requirement Traceability Matrix

Answer Question  Select Best Answer

If an interviewer asks me " Why did you choose software testing?..." then what should I answer....

snehal

• Sep 15th, 2017

In my point of view, giving a true answer is best because they will understand your fake answer about "making customer happy makes me happy" .. so make it simple use your true point of view .. it will be very beneficial for you.

ankit p patel

• Jun 28th, 2017

In my point of view. Best answer of this question is I selected QA because I want to see Customer so happy that he will always remember us. And this is possible when we become error free application.
That's it!!!

Answer Question  Select Best Answer

Mavin

 Profile Answers by Mavin Questions by Mavin

• Dec 15th, 2010

Based on my practical knowledge, organizational experience & knowledge gained through various sources of information, I will try to explain the 5 different CMM levels. As we are moving up in ...

guptvibha

 Profile Answers by guptvibha Questions by guptvibha

• Jul 5th, 2009

CMM - Capability Maturity Model.It is process improvement approach. It can be used to guide process improvement across a project, a division, or an entire organization. It is maturity level for an...

Answer Question  Select Best Answer

Azad khan

• Mar 12th, 2015

The phenomenon of executing the testing activities in systematic and planed way is called software testing life cycle..

Rakesh

• Feb 8th, 2015

1.Testplaning and control
2.Analysis and design
3.Implementation And Execution
4.Evalution and reporting
5.Completion

Answer Question  Select Best Answer

dinesh

• Jan 2nd, 2017

Anitha can you please explain difference b/w developing team and testing team from agile model

palash

• Jun 11th, 2016

Can anyone tell what is example of v model?

Answer Question  Select Best Answer

Read Best Answer

Editorial / Best Answer

Answered by: Sahithi

• Nov 25th, 2005

---

 this matrix defines the mapping between customer requirements and prepared testcases by testengineers.this matrix is requirements traceability matrix or requirements validation matrix.this is used by testing team to verify how far the testcases prepared have covered the requirements of the functionalities to be tested.

Amit

• Aug 28th, 2015

Mapping between test cases or requirement is called traceability matrix.

Bhuvaneshwari K

• Oct 10th, 2014

A traceability matrix is a document, usually in the form of a table, that correlates any two baselined documents that require a many-to-many relationship to determine the completeness of the relations...

Improve Answer

1.what is the difference between regression testing and retesting?in which stage a tester undertakes regression testing and retesting? is both of them same.Explain clearly.2.Is functional testing a part of system testing?3.When a build arrives ,what is t

SONIA25

 Profile Answers by SONIA25 Questions by SONIA25

• May 28th, 2008

Re-Testing "Whenever a fault is detected and fixed the software should  be restested to ensure that the  original fault has been sucessfully  removed" Regresion testing "...

geek_niladri2009

 Profile Answers by geek_niladri2009 Questions by geek_niladri2009

• May 26th, 2008

Regression Testing:-After fix the bugs verify whether new faults are generated or not in the related modules or other module in systemRe Testing:- Repeat the execution of test cases after a bug is fixed to verify the bug has fixed properly.If not fixed properly,Reissue the same.

Answer Question  Select Best Answer