Use Case: A use case is a description of the process which is performed by the end user for a particular task. Use case contains a sequence of step which is performed by the end user to complete a specific task or a step by step process that describe how the application and end user interact with each other. Use case is written by the user point of view.

Use case Testing: the use case testing uses this use case to evaluate the application. So that, the tester can examines all the functionalities of the application. Use case testing cover whole application, tester performs this testing in step by step process to complete one task

For web application we perform following time of test:

1. Functionality Testing.

2. Usability Testing.

3. Navigation Testing.

4. Configuration and Compatibility testing.

5. Reliability and Availability Testing.

6. Performance Testing.

7. Load and Stress Testing.

8. Security Testing

The benefits of Automation Testing are below:

- Test engineer productivity.

- Coverage of regression testing.

- Reusability of test cases.

- Consistency in testing.

- Test interval reduction

- Reduced software maintenance cost

- Increased test effectiveness

Monkey testing is a type of Black Box Testing used mostly at the Unit Level. In this tester enter the data in any format and check the software is not crashing. In this testing we use Smart monkey and Dumb monkey.

- Smart monkeys are used for load and stress testing, they will help in finding the bugs. They are very expensive to develop.

- Dumb monkey, they are important for basic testing. They help in finding those bugs which are having high severity. Dumb monkey are less expensive as compare to Smart monkeys.

Example: In phone number filed Symbols are entered.

EX:

- High Priority and Low Severity:

Company logo is not properly displayed on their website.

- High Priority and High Severity:

Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like "Order has been cancelled."

- Low Priority and High Severity:

If we have a typical scenario in which the application get crashed, but that scenario exists rarely.

- Low Priority and Low Severity:

There is a mistake like "You have registered success" instead of successfully, success is written.

Priority: concern with application from the business point of view. It answers  How quickly we need to fix the bug? Or How soon the bug should get fixed?

Severity: concern with functionality of application. It deals with the impact of the bug on the application.

QA stands for QUALITY ASSURANCE. QA team assures the quality by monitor the whole development process. QA tracks the outcomes and adjusting process to meet the expectation.

The role of Quality Assurance is discussed below:

- QA team is responsible for monitoring the process to be carried out for development.

- Responsibilities of QA team are planning testing execution process.

- QA Lead creates the time tables and agrees on a Quality Assurance plan for the product.

- QA team communicated QA process to the team members.

- QA team ensures traceability of test cases to requirements.

Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.