|
Status for <person's name>
Week-ending <end of week date>
This week:
1. did this
2. did that
3. did the other thing
other details about this and that.
Goals for Next week:
1. do this
2. do that
3. do the other thing
Other details about this and that.
Issues: (both personal and work related)
1. Could not do something else due to something other.
2. Would like to take a vacation next week.
3. Was not able to accomplish the thing I needed to do because of system problems
4. Whatever else might be an issue
WEEKLY STATUS REPORT
(September 28th - November 8th )
Software:
Enterprise Build 21-22
Build Release
somecompany.com
Hardware:
Current test machine: Windows 2000, (NTFS);
64RAM 4GB 2 partitions (C:,D:)
Laptop COMPAQ :Windows '2000 , '98 (32-bit FAT) Dual-Boot
64RAM 4GB 2 Partitions (C: D:)
Types of Test:
Manual Testing (with and without test cases)
Regression Testing
Operating Systems:
Windows 2000 on Test Machine (since sept. 11)
Windows '98 Compaq Presario 1235
Description:
· Tested the new build 12 using the NT and '98. Did regression testing and bug verification.
· Tested Enterprise Build Released Version on Windows '95
· Worked on Enterprise Build 21-22 using Win 2000 on MS Outlook and Lotus
Future Plans:
Interested in new projects.
shared by Konstancia Milova
TEST STATUS REPORT
Date: ____ QA Engineer: _______ Project_________ Email: __________
1.Description of what was tested:
2.System Configuration:
|
System Hardware
|
Operation System
|
Browser & Version
|
Comments
|
| |
|
|
|
| |
|
|
|
3.Procedure used to test:
4.Results, compared to expected results
5.Unexpected results
6.Pass/Fail summary indication
7.Areas required to be tested
8.Accomplishment
9.Bug statistics:
|
Comments
|
New
|
Closed
|
Regressed
|
| |
|
|
|
| |
|
|
|
10.Goals not met from last week
11.Plans for upcoming week
shared by Mikhail Rakhunov
Weekly Status Report
Summary: I know how much reporting scares testers who just begin their career. This sample might
help them a bit.
Available only as a download:
<<WeekelyStatusReport.doc>>
shared by Julie Polyakova
1. Feature that you worked on. (The name of the
feature should match each task name on your schedules)
·Issues related to this feature? Feature Design Changes, blocking bugs, etc.
·Are you on schedule, slipping, ahead? If you are behind, why? Is the feature not ready, blocking bug, etc.
2. If you are working on more than one feature please separate the two.
3. Other Issues that need my attention -Feature Creeps, Vacations, Classes, etc.
 Share your thoughts on Bugs and Fixes in SQAtester Group.
 E-mail to a Friend.
NOTE: This is only a samples of a Status Report. In real environments your Status Report contents
and layout most likely will be different, depends on your project and company requirements.
|
