Difference Between Severity And Priority

Difference Between Severity And Priority

Severity	Priority
Severity: It is with respect to the Impact on the functionality.	It is with respect to the impact on the business.
Example for High Severity: The Quarterly statement event is not triggering from the website and we are just at the beginning of the new quarter after a new release. In this case the Severity is High but priority could be low because we have time till the quarter end to fix the bug.	Example for High Priority: The client logo is not appearing on the web site but the site is working fine. in this case the severity is low but the priority is high because from company's reputation it is most important to resolve. After all the reputation wins more clients and projects and hence increases revenue.

Difference Between Verification And Validation

Difference Between Verification And Validation

Verification	Validation
Are we building the product right?	Are we building the right product?
Verification is to check whether software conforms to the specifications and is done by development team at various development phases.During development phase the SRS document ,Design Document and the code are reviewed to ensure that product is being developed using the process oriented approach.It is an in-house activity of the development organization. It is an Quality assurance activity which prevents the defects of the product.	Validation is to check whether the software meets the customer's expectation.This is done by testing the software for its functionality and other requirements as mentioned in Requirements Specification Documents.Validation is carried out with customer involvement.It is Quality control acitvity which detects the defect during testing of the product

Difference Between Test Scenario And Test Case

Difference Between Test Scenario And Test Case

Test Scenario	Test Case
Test Scenario is ‘What to be tested’	Test Case is ‘How to be tested’
Test scenario is nothing but test procedure.	Test case consist of set of input values, execution precondition, expected Results and executed post-condition developed to cover certain test Condition.
The scenarios are derived from use cases.	Test cases are derived (or written) from test scenario.
Test Scenario represents a series of actions that are associated together.	Test Case represents a single (low level) action by the user.
Scenario is thread of operations	Test cases are set of input and output given to the System.

For example:

• Checking the functionality of Login button is Test scenario
• Test Cases for this Test Scenario are:
• Click the button without entering user name and password.
• Click the button only entering User name.
• Click the button while entering wrong user name and wrong password and etc...

Difference between Verification and Validation in Software Testing

What is the difference between Validation & Verification in Software Testing ?

No.	VERIFICATION	VALIDATION
1	Verification is a static practice of verifying documents, design, code and program.	Validation is a dynamic mechanism of validating and testing the actual product.
2	It does not involve executing the code.	It always involves executing the code.
3	It is human based checking of documents and files.	It is computer based execution of program.
4	Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc.	Validation uses methods like black box (functional) testing, gray box testing, and white box (structural) testing etc.
5	Verification is to check whether the software conforms to specifications.	Validation is to check whether software meets the customer expectations and requirements.
6	It can catch errors that validation cannot catch. It is low level exercise.	It can catch errors that verification cannot catch. It is High Level Exercise.
7	Target is requirements specification, application and software architecture, high level, complete design, and database design etc.	Target is actual product-a unit, a module, a bent of integrated modules, and effective final product.
8	Verification is done by development team to provide that the software is as per the specifications in the SRS document.	Validation is carried out with the involvement of client and testing team.
9	It, generally, comes first-done before validation.	It generally follows after verification.
10	Question Are we building the product right?	Question Are we building the right product?
11	Evaluation Items Plans, Requirement Specs, Design Specs, Code, Test Cases	Evaluation Items The actual product/software.
12	Activities Reviews Walkthroughs Inspections	Activities Testing

Compare Quality-Assurance, Quality-Control, Testing

Comparison of Quality Assurance (QA), Quality Control (QC), Testing ?

No.	Quality Assurance (QA)	Quality Control (QC)	Testing
1	Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives.	Quality Control: A set of activities designed to evaluate a developed work product.	Testing: The process of executing a system with the intent of finding defects. (Note that the "process of executing a system" includes test planning prior to the execution of the test cases.)
2	QA activities ensure that the process is defined and appropriate. Methodology and standards development are examples of QA activities. A QA review would focus on the process elements of a project - e.g., are requirements being defined at the proper level of detail.	QC activities focus on finding defects in specific deliverables - e.g., are the defined requirements the right requirements	Testing is one example of a QC activity, but there are others such as inspections
3	QA is process oriented	QC is product oriented.	Testing therefore is product oriented and thus is in the QC domain.
4	Preventive activities.	It is a antidotal method.	It is a antidotal method.
5	Quality Assurance makes sure you are doing the right things, the right way.	Quality Control makes sure the results of what you've done are what you expected.	Testing for quality isn't assuring quality, it's controlling it.

These are the main differences between Quality Assurance (QA), Quality Control (QC), Testing

Click on the image for Zoom view

Difference between QA and QC are as follows : 

Quality Assurance	Quality Control
1. Quality Assurance helps us to build processes.	1. Quality Control helps us to implements the build processes.
2. It is the Duty of the complete team.	2. It is only the Duty of the Testing team.
3. QA comes under the category of Verification.	3. QC comes under the category of Validation.
4. Quality Assurance is considered as the process oriented exercise.	4. Quality Control is considered as the product oriented exercise.
5. It prevents the occurrence of issues, bugs or defects in the application.	5. It always detects, corrects and reports the bugs or defects in the application.
6. It does not involve executing the program or code.	6. It always involves executing the program or code.
7. It is done before Quality Control.	7. It is done only after Quality Assurance activity is completed.
8. It can catch an error and mistakes that Quality Control cannot catch, that is why considered as Low Level Activity.	8. It can catch an error that Quality Assurance cannot catch, that is why considered as High Level Activity.
9. It is human based checking of documents or files.	9. It is computer based execution of program or code.
10. Quality Assurance means Planning done for doing a process.	10. Quality Control Means Action has taken on the process by execute them.
11. Its main focuses on preventing Defects or Bugs in the system.	11. Its main focuses on identifying Defects or Bugs in the system.
12. It is not considered as a time consuming activity.	12. It is always considered as a time consuming activity.
13. Quality Assurance makes sure that you are doing the right things in the right way that is the reason it is always comes under the category of verification activity.	13. Quality Control makes sure that whatever we have done is as per the requirement means it is as per what we have expected, that is the reason it is comes under the category of validation activity.
14. QA is Pro-active means it identifies weaknesses in the processes.	14. QC is Reactive means it identifies the defects and also corrects the defects or bugs also.

Click on the image for zoom view

Click to read about Differences between Black Box and White Box Testing , Differences between Black box, White box, Gray box testing

Differences between Black box, White box, Gray box testing

What are the Differences between Black Box / White Box / Gray box Testing ?

Note that Gray is aswell spelt as Grey. Hence Grey Box Testing and Gray Box Testing beggarly the same.

Click on the image for zoom view

Click to read about Differences between Black Box and White Box Testing , Compare Quality-Assurance, Quality-Control, Testing

Differences between Black Box and White Box Testing

What is the differences between Black Box Testing and White Box Testing ?

Here are some common differences between Black Box Testing and White Box Testing :

Criteria	Black Box Testing	White Box Testing
Definition	Black Box Testing is a software testing method in which the internal structure/ design/ implementation of the item being tested is NOT known to the tester	White Box Testing is a software testing method in which the internal structure/ design/ implementation of the item being tested is known to the tester.
Levels Applicable To	Mainly applicable to higher levels of testing:Acceptance Testing System Testing	Mainly applicable to lower levels of testing:Unit Testing Integration Testing
Responsibility	Generally, independent Software Testers	Generally, Software Developers
Programming Knowledge	Not Required	Required
Implementation Knowledge	Not Required	Required
Basis for Test Cases	Requirement Specifications	Detail Design

Click to read about Differences between Black box, White box, Gray box testing

Manual Testing vs Automated testing

Discuss about adverse between Manual Testing vs Automated testing :

• Manual testing is an simple action as compared to automatic testing. Automated testing is beneath time balance as compared to chiral testing.

• Manual testing is accessible up to assertive akin but Automatic testing is accessible at every level. Automated testing is added big-ticket as compared to chiral testing.

• Manual testing is acclimated for baby projects where-as Automatic testing is acclimated for continued appellation projects.

• Manual testing is based on functions and abstraction of the activity but the abutment of Automatic testing is bound to few languages.

• Manual Testing requires circuitous Chiral Setup and tears down, admitting Automatic Tests can accept been capricious scopes and crave beneath circuitous setups and teardown.

• Manual Testing has a top accident of missing out on something, admitting Automatic Tests accept aught risks of missing out a pre-decided test.

• Manual Tests do not accommodate a safety-net, admitting Automatic Tests accommodate a safety-net for refactoring / additions.

Read more about Automation Testing and Manual Testing vs Automated testing

Difference between Manual testing and Automation testing

What are the differences between Manual testing and Automation testing ?

• Executing the test cases manually without any tool support is known as manual testing.
• Taking tool support and executing the test cases by using automation tool is known as automation testing.
• Following table shows the difference between manual testing and automation testing.

Manual Testing	Automation Testing
1. Time consuming and tedious: Since test cases are executed by human resources so it is very slow and tedious.	1. Fast Automation runs test cases significantly faster than human resources.
2. Huge investment in human resources: As test cases need to be executed manually so more testers are required in manual testing.	2. Less investment in human resources:Test cases are executed by using automation tool so less tester are required in automation testing.
3. Less reliable: Manual testing is less reliable as tests may not be performed with precision each time because of human errors.	3. More reliable: Automation tests perform precisely same operation each time they are run.
4. Non-programmable: No programming can be done to write sophisticated tests which fetch hidden information	4. Programmable: Testers can program sophisticated tests to bring out hidden information.

What is Acceptance Testing - Alpha, Beta Testing

What is Acceptance Testing :

This is arguably the most importance type of testing as it is conducted by the Quality Assurance Team who will gauge whether the application meets the intended specifications and satisfies the client.s requirements. The QA team will have a set of pre written scenarios and Test Cases that will be used to test the application.

More ideas will be shared about the application and more tests can be performed on it to gauge its accuracy and the reasons why the project was initiated. Acceptance tests are not only intended to point out simple spelling mistakes, cosmetic errors or Interface gaps, but also to point out any bugs in the application that will result in system crashers or major errors in the application.

By performing acceptance tests on an application the testing team will deduce how the application will perform in production. There are also legal and contractual requirements for acceptance of the system.

When is it performed?

Acceptance Testing is performed after System Testing and before making the system available for actual use.

Who performs it?

• Internal Acceptance Testing (Also known as Alpha Testing) is performed by members of the organization that developed the software but who are not directly involved in the project (Development or Testing). Usually, it is the members of Product Management, Sales and/or Customer Support.
• External Acceptance Testing is performed by people who are not employees of the organization that developed the software.
• Customer Acceptance Testing is performed by the customers of the organization that developed the software. They are the ones who asked the organization to develop the software for them. [This is in the case of the software not being owned by the organization that developed it.]
• User Acceptance Testing (Also known as Beta Testing) is performed by the end users of the software. They can be the customers themselves or the customers’ customers.

Definition by ISTQB for Acceptance Testing

Formal testing with respect to user needs, requirements, and business processes conducted to determine  whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.

Define Alpha-Beta Testing :

Alpha Testing

This test is the first stage of testing and will be performed amongst the teams (developer and QA teams). Unit testing, integration testing and system testing when combined are known as alpha testing. During this phase, the following will be tested in the application:

• Spelling Mistakes
• Broken Links
• Cloudy Directions

The Application will be tested on machines with the lowest specification to test loading times and any latency problems.

Beta Testing

This test is performed after Alpha testing has been successfully performed. In beta testing a sample of the intended audience tests the application. Beta testing is also known as pre-release testing. Beta test versions of software are ideally distributed to a wide audience on the Web, partly to give the program a "real-world" test and partly to provide a preview of the next release. In this phase the audience will be testing the following:

• Users will install, run the application and send their feedback to the project team.
• Typographical errors, confusing application flow, and even crashes.
• Getting the feedback, the project team can fix the problems before releasing the software to the actual users.
• The more issues you fix that solve real user problems, the higher the quality of your application will be.
• Having a higher-quality application when you release to the general public will increase customer satisfaction.

Testing (vs) Debugging differences between

Discuss the differences between Testing vs Debugging:

Testing

Testing activity is carried down by a team of testers, in order to find the defect in the software. Test engineers run their tests on the piece of software and if they encounter any defect (i.e. actual results don't match expected results), they report it to the development team. Along with the nature of defect, testers also have to report at what point the defect occurred and what happened due the occurrence of that defect. All this information will be used by development team to DEBUG the defect.

Debugging

Debugging is the activity which is carried out by the development team (or developer), after getting the test report from the testing team about defect(s) (you may note defects can also be reports by the client). The developer then tries to find the cause of the defect, in this quest he may need to go through lines of code and find which part of code in causing that defect. After finding out the bug, he tries to modify that portion of code and then he rechecks if the defect has been finally removed. After fixing the bug, developers send the software back to testers.

Testing vs Debugging:

Click on the image for Zoom view