What is the difference between Severity and Priority?

There are two key things in defects of the software testing. They are:
1) Severity
2) Priority

What is the difference between Severity and Priority?

1) Severity:

It is the extent to which the defect can affect the software. In other words it defines the impact that a given defect has on the system. For example: If an application or web page crashes when a remote link is clicked, in this case clicking the remote link by an user is rare but the impact of application crashing is severe. So the severity is high but priority is low.

Read More

Difference between Test case and Test scenario:

Difference between Test case and Test scenario:

Test case consist of set of input values, execution precondition, excepted Results and executed post condition, developed to cover certain test Condition. While Test scenario is nothing but test procedure.

A Test Scenarios have one to many relation with Test case, Means A scenario have multiple test case. Every time we have write test cases for test scenario. So while starting testing first prepare test scenarios then create different-2 test cases for each scenario.

Test cases are derived (or written) from test scenario. The scenarios are derived from use cases.

Read More

Guidelines for Functional Test Cases

We generally need to follow the Guidelines for Functional Test Cases as per our test process. Some of the information giving you…..

Build use case scenarios as indicated below

Understand and analyse use case from SRS.

Create Scenarios with conditions for each Use cases (Refer UML modelling for details)

For each scenario/condition, write test cases with detailed steps and identify expected output

Write test cases for special requirements of each use case.

Identify Test data as indicated below:

Identify the domain values of each parameter.           

E.g.   a person is eligible for insurance program if he meets the age requirement as 18 to 64 (as per mentioned in admin module) then BVA analysis should be in following way for this requirement

Read More

Non-Functional Testing

Non-Functional Testing

Testing the application based on the clients and performance requirement.

Non-Functioning testing is done based on the requirements and test scenarios defined by the client.

Non-Functional testing covers

• Load and Performance Testing

• Ergonomics Testing

• Stress & Volume Testing

• Compatibility & Migration Testing

• Data Conversion Testing

• Security / Penetration Testing

• Operational Readiness Testing

• Installation Testing

• Security Testing (Application Security, Network Security, System Security)

Read More

Functional Testing

Functional Testing

Testing developed application against business requirements.

Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.

Functional testing covers

• Unit Testing

• Smoke testing / Sanity testing

• Integration Testing (Top Down, Bottom up Testing)

• Interface & Usability Testing

• System Testing

• Regression Testing

• Pre User Acceptance Testing (Alpha & Beta)

• User Acceptance Testing

• White Box & Black Box Testing

• Globalization & Localization Testing

Read More