Bug Report - Sample Issue Documentation

Issue Summary:

Admin – Login page does not show up any validation messages

URL:

http://server2/Scar%20Global%20Life%20Insurance2/AdminLogin.aspx

Navigation:

Home Page – Admin - Login

Steps to reproduce the issue:

ž Navigate to SGIS – Home page using URL : http://server2/Scar%20Global%20Life%20Insurance2/Default.aspx

ž Click on the Admin link from the footer menu

ž Observe that Admin login page loads up

ž Try hitting the LOGIN button without entering any user name and password data

ž Observe that there are no validation messages shown up

Observation:

Though there are red asterisk symbols shown up, it could be expected to have validation messages

Snapshot:

Testing Methodologies

Testing Methodologies / Testing Strategies:

Testing Methodology is a Scheme / Approach / Strategy that explains what kind of methodology can be utilized at different phases of the SDLC.

Testing Methodologies are also called testing strategies.

There are 3 Testing Methodologies available.

1) Black Box Testing

2) White Box Testing

3) Gray Box Testing

1) Black Box Testing:

(This is especially for Testers).

It is also called as Functional Testing (Functional based Testing).

It is also called as requirements based Testing.

Definition: The process of testing the application without consideration of the code but with consideration of the Functionalities / Requirements of the application.

In Black Box Testing, Testers will never bother about the code and Testers will not bother about the software environments. (Software environment = coding language).

Testers will mainly focus on requirements and the behavior of the application (Functionality of the application), based on the functional requirements testers will have to design test plans and test cases.

And later what is the coding is done application build is release to QA and now testers will execute the Functional Test Cases on the application build.

Black Box testing has the following testing types as part of it.

1) Smoke Testing

2) Functional Testing.

3) Integration Testing

4) System Testing

5) Regression Testing

6) Automation Testing

7) UAT

2) White Box Testing:

(This is especially for developers).

This is also called structural testing (structural base to testing).

This is also called code based testing.

This is also called clear based testing.

Definition: The process of testing the application with consideration of the code (like loops, structures, conditional statements, Functions, Procedures, and Structures and so on) focusing the code level executions.

Developers consider each and every Module level code, all the loops, conditions, functions in their code and so foe such White Box Testing.

White Box testing as following testing types as part of it.

1) Unit Testing

2) Integration Testing

a. Top-down approach

b. Bottom-up approach

c. Hybrid-approach

d. Big-Bang approach

3) Code base Testing

a. Statement coverage

b. Loops coverage

c. Functional coverage

d. Module coverage

3) Gray Box Testing:

The process of testing the application in both the considerations like considering the code and considering the functionalities of the application is called as Gray Box Testing.

This is also called as Hybrid Testing.

With the gray box testing methodology we lose both the White Box Testing methodology and Black Box testing methodology while testing the application.

Usually this kind of testing is carried out by the developers who have testing experience also (person = Dev + QA).

Roles and Responsibilities of Testers

Roles and Responsibilities of Testers

Test manager:

à SPOC for any QA related activities

à Estimating test efforts and schedule the testing process.

à Act as an interface between the testing team and development team

à Carry out QA requirements analysis.

à Test and review the requirements and provide feedback to the Business Analysis team.

à Coordinate QA activities with complete QA tasks.

à Review all QA deliverables from Company.

à Scenario Test Case design and review test cases

à Participate for the Defect Review meetings

à Defect Tracking and Management.

à Co-ordinate with Onsite / Offshore QA

à Execute the Acceptance testing for Customer

Test lead:

à Primary contact for QA activities for App

à Prepare the Quality Assurance Test Plan.

à Carry out QA requirements analysis.

à Test and review the requirements and provide feedback to the Business Analysis team.

à Coordinate QA activities and complete QA tasks.

à Review all QA deliverables to Onsite.

à Design and Review QA Test Cases.

à Design the Test Automation Procedures.

à Conduct Sanity, Functionality, Integration, System and Regression, UI testing on the required components with the team.

à Defect Tracking and Management.

à Create Defect Summary Reports and Test Results document.

à Set up the QA test environment.

à Assist the team members in creating test data.

à Create the QA Release Note.

à QA Status updates

QA Engineer / Test Engineer (Tester):

à Understand customer requirements

à Understand QATP, test strategy

à Develop test cases according to Reqs / FRS / SRS / Use Cases / Test plans

à Review and update test cases

à Execute test cases

à Log detail defect report

à Involve in Sanity, Functional, Integration, System, Regression, and Defect Verification testing

à Participate in Automation Testing

à Provide accurate and detailed weekly task reports

à Update traceability metrics

àAssist QA Lead for ensuring successful delivery