Software Testing Defect Reporting - Definition, Composition, Defect Lifecycle, Defect Tracking Post-Production Process, Defect Tracking Process, Purpose of Defect Tracking, Defect Management Tools

Software testing defect reporting - definition, composition, defect life cycle, defect tracking post-production process, defect tracking process, purpose of defect tracking, defect management tools

I. Definition:

1. The unimplemented requirements specification specifies the requirements to be implemented (explicit requirements)

2. Unimplemented requirements that are not specified in the requirements specification but should be implemented (implicit requirements)

3. Exceeding the scope specified in the requirements specification

4. There is a bug that indicates that it will not appear

5. The user experience is not good, the use is not good, the operation is not easy, and the operation is slow

2. Composition:

Defect title: Summarize in one sentence, in which module, XX operation was done, and XX problem occurred

Problem description: operation steps + expected results + measured results + remarks (probabilistic problems, in the remarks, how many times to test and how many times)

Severity: fatal, severe, moderate, minor, improvement suggested

Priority: resolve immediately, high priority, normal queue, low priority

Defect Status: New, Open, Repair, Rejected, Active, Deferred, Repeated, Closed

Probability of defects: must occur, occasional, non-reproducible (or 10%-100% can be written)

Software version: Vxxx, for example, V12.8.0

Operating system: operating system on b/s side (browser server side): Win (XP, 7, 10, 11), Linux (centerOS6); operating system on c/s side (client server side):Android, Hongmeng, ios, etc.

Browser: IE series (6-11), chrome, Firefox series (2-4), UC, etc.

Assignee: Assigned to Development Engineer

Submitted by: Test Engineer

Submission time and modification date: the day when the problem was discovered

The module to which the defect belongs:

Operation steps:

Attachments:

Three, the life cycle of defects: there are multiple life cycles

Simple Cycle: Discover-Open-Repair-Close

Complex cycle: Discover-Open-Reject-Activate-Repair-Close

Other: Discover-Open-Repair-Reproduce-Repair-Close

Discover-Open-Delay-Repair-Close

Fourth, defect tracking process:

1. The tester gets the new version and executes the test

2. Find defects and submit bugs in the defect management tool

3. Developers fix bugs

4. For problems that cannot be repaired or repaired, TOCCB (Expert Tribunal) determines how to solve them

5. Development check in and submit the code to the code server

6. The builders merge the code, compile the new version, and upload it to the SVN server

7. The tester obtains the new version from the SVN server and starts a new round of testing

V. Purpose of defect tracking:

Defect analysis, software measurement

Six, defect management tools: integration of project management, task management and defect management

Defect tools: Zen Tao, jira, QC, TD

Now I invite you to join our software testing learning exchange group: [746506216], note "join the group", everyone can join togetherDiscuss and communicate software testing, learn software testing techniques, interviews and other aspects of software testing together. There will also be free live classes to gain more testing skills. Let's advance Python automated testing/test development together and move towards a high-paying careerroad.

Friends who like software testing, if my blog is helpful to you, if you like my blog content, please "Like", "Comment" and "Favorite" with one click!