Site Content

image15

Filling out tHE TEST REPORT

 1. ISSUE TITLE

For Issue title follow the standard as below

Environment - Area of test - Brief issue

Environment would mean the device os like Windows 10 or Android A71.

Area of test would mean the area of the application like Profiles and Settings, Customer creation etc..

Brief issue would mean a brief description of the issue.


 

2. Issue Classifications

Select the correct bug classifications to explain what type of bug is being reported, how often it occurs, what environments were used and the impact of the bug to the user.

  • Issue Type: Functional, Visual, Content, Performance or Crash 
  •  Frequency: Every Time, Hardly ever, Occasionally or Once
  • Device and environment: Must be selected correctly and match the title
  • Severity: Critical, High, Medium, Low.


3. TEST STEPS

Describe how to reproduce the bug by writing numbered steps in the actions performed field.

  • 3.1 Use numbered steps to show how to recreate the bug
  • 3.2 Write only one task on each step
  • 3.3 Begin the numbered steps from the URL of the website or opening the app
  • 3.4 Do not write "observe, check, or view result" in the numbered steps
  • 3.5 Do not write the expected or actual results in the numbered steps

4. Expected Results

Describe exactly what the user would expect to happen when carrying out the steps in the actions performed.


5. Actual Results

Describe exactly what does happen when the user carries out the steps in the actions performed.


6. Error Message

Only use this field if there is an error message when recreating the bug. Write the full error message that is displayed on the screen if the bug results in an error message.


7. Screenshots

Include a screenshot with every bug report and clearly highlight the bug as it appears on the screen.

  • 7.1 Add a red or yellow square, circle or arrow to highlight where the bug appears
  • 7.2 Upload in .jpg or .png format
  • 7.3 Capture the entire screen (Including the URL bar for web testing)
  • 7.4 Verify that the screenshot can be opened inside the platform after submitting the report
  • 7.5 Do not upload more than 2 screenshots per bug report

8. Videos

Include a video showing all the steps required to recreate the bug. The video needs to match the steps listed in the actions performed.

  • 8.1 Upload videos in .MP4 format
  • 8.2 The video needs to match the steps listed in the actions performed
  • 8.3 Show the entire screen (Including the URL bar for web testing)
  • 8.4 Mute the microphone to exclude background noise (Unless narrating is required)
  • 8.5 Verify that the video can be played inside the platform after submitting the report
  • 8.6 The bug being reported must appear in the video
  • 8.7 Don't record a computer screen with a mobile phone, use software

9. Computer & Mobile Logs

Include a device log or a console log with every bug report.

  • 9.1 Save logs in .txt format (Charles logs need to be saved in .chls format)
  • 9.2 Verify the test URL is visible in the data entry lines in the log
  • 9.3 Enable "Preserve or Persist log and Show Timestamp" in Chrome and Firefox
  • 9.4 Click the links below to learn how to capture logs

10. Charles Proxy Logs

Include a decrypted Charles proxy log with every bug report when requested.

  • 10.1 All data must be decrypted in Charles logs (Only access the test website when collecting Charles logs)
  • 10.2 The root certificate must be installed correctly on the computer and mobile device (If the certificate wasn't installed correctly, the expanded items will show an < unknown > message)
  • 10.3 Configure the required SSL settings (host * and port 443)
  • 10.4 Upload the entire Charles log. After reproducing the issue, click on file, then click 'save session as.