The Bug Tracking System role is discussed below:

- Testers and developers can know the status of the bug at every stage.

- Changes to the Status will be available to all team members.

- Developers and Testers can easily interact with bugs.

- Repetition of bugs will be avoided.

- Easy to distribute the bug among the developer.

- It will act as a centralized one for defects.

The differences in responsibilities are listed below:

- QA is concern for Process Quality and Programmers are concern for Product Quality.

- QA ensure that the processes used for developing the product of high quality where as programmers used these processes so that end product is of good quality.

- Processes are decided by QA. Programmers are supposed to follow the processes so that they can produce a good quality product.

- Any issue found during execution of process by the programmers is communicated to the QA so that they can improve the process.

The main attributes are discussed below:

Maintainability: For each new release need to update the test automation suites.

Reliability: Accuracy and repeatability of the test automation.

Flexibility: Ease of working with all the different kinds of automation test ware. 

Efficiency: Total cost related to the effort needed for the automation.

Portability: Ability of the automated test to run on different environments.

Robustness: Effectiveness of automation on an unstable or rapidly changing system. 

Usability: Extent to which automation can be used by different types of user.

First thing testers are not responsible for fixing the bug they are only responsible for debugging the bug and prioritizing those bugs. These bugs are now reported in bug report template with the severity and priority of the bug. Tester assigns severity level to the defects depending upon their impact on other parts of application. Every bug has its severity and priority values assign by tester. If a defect does not allow you to go ahead and test the product, it is critical one so it has to be fixed as soon as possible. We have 5 levels as:

Critical

High

Medium

Low

Cosmetic

Time Estimation method for Testing Process:

Step 1 : count number of use cases (NUC) of system 

Step 2 : Set Avg. Time Test Cases(ATTC) as per test plan 

Step 3 : Estimate total number of test cases (NTC) 

Total number of test cases = Number of Use Cases X Avg. Test Cases per a use case 

Step 4 : Set Avg. Execution Time (AET) per a test case 

Step 5 : Calculate Total Execution Time (TET) 

TET = Total number of test cases * AET 

Step 6 : Calculate Test Case Creation Time (TCCT)

usually we will take 1.5 times of TET as TCCT

TCCT = 1.5 * TET

Step 7 : Time for Re-Test Case Execution (RTCE) this is for retesting

usually we take 0.5 times of TET

RTCE = 0.5 * TET

Step 8 : Set Report generation Time (RGT

usually we take 0.2 times of TET

RGT = 0.2 * TET

Step 9 : Set Test Environment Setup Time (TEST)

it also depends on test plan

Step 10 : Total Estimation time = TET + TCCT+ RTCE + RGT + TEST + some buffer.

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