2
Status Reports: Purpose: 1. part of Project Management 2. monitoring and managing the project deliverables 3. part of project standards like SEI CMMI Levels Types of Status Reports Daily status Report: Email at the end of the day to the Test LEad mentioning abo ut the status of the assigned tasks Daily Defect Report: Email at the end of the day to the Test LEad mentioning abo ut the status of the defects identified in a daily defect report template. enclo sed as an attachment daily defect report template Sl.No Defect Id Defect Title Severity Logged by Logged Date Weekly Status Report: Every week you will be sending across the weekly status r eport as an attachment. Weekly status Report Template: Project Code Week Ending Project Name Test Engineer: High Level Summary: Major Accomplishments since last reporting period Tasks not completed as planned defects Summary by severity Sl.no Defect ID Severity Effort summary Risks and issues Retesting Report: Test lead will assign the fixed defects for Retesting. Test engineers will perform retesting on all the fixed defects against new build . They will update the status in Bugzilla - bug tracking tool. They will prepare a Retesting template to forward to the test lead. ReTesting Report Template: Sl.No DefectId Title Severity Test Engineer Fixed in version Fixed in which build Status before ReTest Status After Retest

Status Reports, WEB Application Testing

Embed Size (px)

Citation preview

Page 1: Status Reports, WEB Application Testing

Status Reports:

Purpose:1. part of Project Management2. monitoring and managing the project deliverables3. part of project standards like SEI CMMI Levels

Types of Status Reports

Daily status Report: Email at the end of the day to the Test LEad mentioning about the status of the assigned tasks

Daily Defect Report: Email at the end of the day to the Test LEad mentioning about the status of the defects identified in a daily defect report template. enclosed as an attachment

daily defect report template

Sl.No Defect Id Defect Title Severity Logged by Logged Date

Weekly Status Report: Every week you will be sending across the weekly status report as an attachment.

Weekly status Report Template:

Project Code Week Ending

Project Name Test Engineer:

High Level Summary:

Major Accomplishments since last reporting period

Tasks not completed as planned

defects Summary by severity

Sl.no Defect ID Severity

Effort summary

Risks and issues

Retesting Report: Test lead will assign the fixed defects for Retesting.Test engineers will perform retesting on all the fixed defects against new build.They will update the status in Bugzilla - bug tracking tool.They will prepare a Retesting template to forward to the test lead.

ReTesting Report Template:

Sl.No DefectId Title Severity Test Engineer Fixed in version Fixed in which build Status before ReTest Status After Retest

Page 2: Status Reports, WEB Application Testing

Web Application Testing:

CITIBANK (Database Server in USA) -

CITIBANK UK (Linux/Unix, Firefox 5.0) (Request and Response)CITIBANK INDIA (windows xp, I.E 9.0) CITIBANK CHina (........CITIBANK USA CITIBANK GERMANY

Purpose: world wide web is browsed by customers world wide with different levels of knowledge. testers have to concentrate on various aspects of static and dynamic testing.

Aspects to cover:

Functionality: links (Testing internal links, external links, email links), forms (Fields validation, Error messages for wrong inputs, Optional fields and mandatory fields)Database (Data validation, data integrity)cookies (on temporary internet files)

usabilityusability testing is testing process by which the end user interaction characterisitics of the system will be measured and weaknesses are identified for correction.

1. ease of learning 2. navigation 3. satisfaction levels 4. appearance

User Interface: look and feel, alignment, font size, color, format, ,.....

Compatibility: operating systems and browser compatibilities

security: valid and invalid loginlimits defined for the no of triesbypassing by typing the URL of the page.verify the log files are maintained to store the information for traceability.verify the encryption is done correctly or not.if the website is idle for 10 to 15 mins , then the sessin should expire

performance:

website scalability connection speedload - no of users per time, peak load and how the system is behaving, large amount of data accesed by user

stress - continuous load, performance of memory, cpu etcserver side interface: compatibility of server with software, hardware, database, network......