Test Department work Check Point of view

This morning read a post, introduced that Google, Intel, LinkedIn these companies have given up KPIs, special Okr. Curious to see the explanation of Okr. After reading, can not say no harvest, just feel like in the present own department to implement still have quite many difficulty. Click here for friends who want to know.

As a test department leader, sometimes have to do some mandatory requirements and inspection Department, anyway, I always feel that the management of the theory is not important, it is important whether the theory can solve the actual problem, whether it applies to their own company.

This morning to tidy up the requirements of the Test Department, welcome to Exchange.

Number	Type	Check Opinion	Note
1	Daily Mail	Before you start your test work, you need to send the current version of the test case or test point as a message to the team and CC the project team to avoid leakage. Message name: "Test scope" XXXX Project XXXX version test range _YYYYMMDD	Patch not required; bug fix release submit checklist to check if new issue is changed
2		The current version of the test results and test reports will be sent to the department full and copied to the project team the same day after the release test is completed. Message name: "Test results" XXXX project XXXX version test results _YYYYMMDD	The end of the X5 is subject to the test report's time of issue
3		Daily project daily to be sent during the test Message name: "XXXX project" test situation _YYYYMMDD
4	Bronze defects	The problems found during the test are to register the bronze ware, avoid verbal reminders, and follow the circumstances that cannot be traced.
5		The number of defects submitted varies according to the project phase submission quantity criteria, depending on the situation.	How many bugs can be found is a relatively objective measure of the effectiveness of the work
6		The quality of the submission of defects, i.e. the value of submitting defects. In general, the value of the UI is low, but the value of business defects is relatively high.	Try to identify problems from the user's business level
7		Test case completion to meet departmental requirements (defect level, recurrence steps, logs, etc.), so that other people can clear the understanding of the two, the necessary information to provide a complete	Reduce communication costs
8	Test Plan	Whether the risks (new technology, duration, test environment limits, etc. ) are taken into account
9		Whether the workload assessment is accurate	Avoid too much tension and too loose to ensure test quality
10	Test Cases	Each system must have a test case or test point, identify the work needs to reserve test case writing time
11		Whether the use case is completed on time
12		Consider whether thoughtful and comprehensive
13		Is there a better test method for organizing training and sharing?
14		Test cases conform to departmental requirements for test cases (format, priority recognition, etc.)
15	Test report	Test report should be published in time, in principle, the date of the completion of the test is sent by mail, special circumstances need to communicate in advance
16		The information in the test report should be accurate, can not appear before and after the data obviously to not rise and other similar problems
17		do you give instructions for failed, locked use cases?
18		Did the failed use case explain why?
19		Do you report serious problems and risks in a timely manner and confirm with the development communication?
20		Whether the test report can truly reflect the actual situation of the project and will not mislead the project stakeholders
21st	Work Tasks & execution	The input time for each task needs to be clearly described, and the time required to describe each job is needed for multiple tasks to fill in a large task.	Fill in the input time according to the actual investment
22		Each task must upload the output to VSS or SVN and clear the output path when the bronze is submitted to the task
23		Work time inputs are proportional to output outputs, and there is a clear need for serious deviations.
24		Can you test from a user and business perspective and consider possible problems outside of use cases
25		Whether the test task can be completed in time or even ahead
26		Can we proactively promote problem solving
27		Is it possible to refine a good working method and organize training for analysis
28		What types of bugs are missing?
29	Bronze	The bronze version process needs to be updated on the day of completion when the version is tested
30		Defects should be updated on the day after the defect is returned so that the development can be carried out smoothly.
31		Bronze work log needs to be completed before the end of every day
32	Other	How do you do in keeping with your promises?
33		Are you learning new skills? How is it done to impart your skills to other testers?
34		What problems have you dealt with on the company's stand?

(0 0)
+------OOO---(_)------------+
| |
| "Welcome attention" |
| Miss Zhang's Little black House |
+--------------------OOO-----+
|__|__|
|| ||
Ooo ooo

Test Department work Check Point of view