Testing Process Real time End-to-End

Testing Process End-to-End

1.      FRS REVIEW :

FRS means Functional Requirement Specification.

This requirement directly given by Customer. First of all we need to understand all the requirements very clearly. We should know what customer is expecting. Each and every software company will give 15-20 days for only FRS Review.

2. TEST PLAN REVIEW:

Usually Test plan prepared by Test Lead. How to complete particular project successfully. He will List out all the points very clearly in the Test Plan Document.

We need to follow the Test Plan .It is very important to the project.

3. BRS REVIEW:

First of all we should know what the main difference between BRS and FRS is

FRS: This is the customer final Requirements. This document consists of all the customer functional and nonfunctional requirements.

BRS: This document prepared by Business People or Business analyst. The Business tells “what” they want for the application to do.

In simple words BRS contain the functional requirements of the application.

We need to review the BRS.While doing review if you have any doubts we will list out in review report and we will send to Business analyst that means  Reporting.

4. Participating the Review meetings:

Each and Every software company they will conduct Review meetings for sharing the information. They conduct these Review meetings. So we will be participating the Review meetings.

5. Identifying the Scenario’s:

Before writing the Test cases we need to find out test scenarios.

For Example: We have one login application; we need to test’s we need to enter username and password. We need to click on login button. This is one scenario. So we need to identify all the scenarios in the application.

6. Prioritizing the scenarios:

First of all we should know what you mean by Priority.

For Example we have some defects.

In what sequence defect has to be rectified.

It is classified into four types.

1.      Critical

2.      High

3.      Medium

4.      Low

Based on the situation we will give the priority.

7. Designing the Test Cases:

Test case is nothing but it is an idea of Test Engineer. Based on the customer requirements we will write the test cases. Each and every software company will maintain own Test case Template.

8. Involving the Peer Review:

Peer means Colleague. We need to Participate Peer review meetings. Usually we will involve into peer reviews.

9. Sending the TCD to lead for Lead Review:

After writing the test cases we need to send the Test Case document to lead. If there is any correction he can do.

10. Refining the design based on peer or lead comments:

After conducting the peer review and lead review If they give any comments and suggestions we need to follow. Simply we can say fine tuning we will rectify all the mistakes.

https://www.youtube.com/watch?v=SvSZaqG9yaA

11. Getting the approval for the design from BA:

Whenever getting the approval from Business analyst we will execute the test cases.

12. SRN Study, understanding the scope:

SRN means software Release Note. It is a note prepared by Technical department people and sent to testing department. It contains

Build Path Information

Test data Path Information

Deployment document path information

Known Issues Path Information

Released Manager Name

Released date

Build number

Version number

Project name

Module name

After studying we will estimate the scope.

13. Deployment Document Study:

Deploying the build into the test environment. Each and every software company people will prepare deployment document. Deployment document means it is a set of instructions.

“How to install the application into customer specified environment”

They will prepare set of guidelines using these guidelines. We will install the application into that environment.

14. Conduct Sanity Testing:

This is one of the type of testing. Initially we will perform sanity testing. After releasing the build development department to testing department. We will do this Sanity testing.

‘Why we will do: In order to check whether it is proper for further detailed testing or not. There is any scope to perform testing or not. We will check.

15. Processing the Functional Testing:

Functional Testing means we will perform actions on the functionality, then only we can say that functionality properly working or not.Customer expected result is coming or not. So we will do functional testing.

16. Defects Reporting:

After finding the defects we need to raise the defect to development department. For that each and every software company they will provide defect profile Template using this Template we will raise the defect to developers.

This defect profile Template contains

Defect ID

Defect description

Steps for reproducibility

Submitter

Date of Submission

Build Number

Assigned To Fields

Then only developers will accept the defects.

17. Getting the Modified Build from development team:

Whenever you are raising the defect developers will rectify the defect and once again they will send to testing department. Once again we will perform testing on the modified build.

18. Re and Re-gression testing on the modified build:

After getting the modified build we will perform different, different types of testing like Re-testing and Regression Testing.

Regression Testing means we will perform testing on the already tested functionalities again and again.

Retesting means we will test the functionality again and again with multiple sets of data or different sets of data.

19. Performing System Testing:

After installing the application we will perform different, different types of testing. We will perform negative testing and positive testing also.

“Why will do negative testing”

In order to find out the stability of the application. A Test Engineer Should has negative mindsetup.Then only he will become a good Test engineer. Whenever we are doing negative testing we can get more defects.

20. Test Closure:

Test Closure document is nothing but the document which is having the details of test pass as well as test fail results. That means in test case document how many test cases passed, and how many test cases failed we will prepare one document that is test closure.

This is total end to end testing process

For video please visit below link

https://www.youtube.com/watch?v=SvSZaqG9yaA