Log in to FieldFX Mobile with the 'QA Field' user.
Generate an error for the back office audit log. E.g Delete a job in back office and add a ticket in mobile then sync or trigger a back office validation error.
Go to back office and click on the related Audit log ID.
Click on the URL link. You may be required to login. Use your back office admin login.
Click on the URL link again.
Expected Result
You are taken to the new static message " This page has been replaced with the Packet Viewer or Sync Events Viewer. Please use these tools instead of this page"
| | |
|-|-|
1
|
Ensure the defect title and description is clear and understandable.
|
|
2.
|
Ensure the following are listed on the card:
* Mobile or back office version.
* Operating system
* Devices
* Browsers
* Username/Password.
|
|
3.
|
Ensure there are steps to reproduce and are easy to follow.
Add screenshots as necessary for clarity
|
|
4.
|
Ensure the Expected and Actual results are listed.
|
|
5.
|
Check whether the bug exists in production (Sync V4) and/or Sync V4 Beta
* If the bug exists in current production then select the “**Sync V4 Channel”**
* If the bug exists in the Beta Channel but is not in production yet, then select “**Beta Channel”**
* If the bug was created during current iteration then select "**Regression**”
|
|
Test Plan
| | |
|-|-|
1.
|
Ensure the card has enough information from the programmer before you start the verification
If not request more information
|
|
2.
|
Ensure you’re able to reproduce the defect prior to verifying it
|
|
3.
|
Ensure to verify if the PR is still valid by going to Github.
|
|
3.
|
Create a test plan and write/update test case for the card is there is no test case in Tarantula.
|
|
4
|
Test the card on all required devices and versions. If it’s a mobile card, always test the offline functionality around that defect. Attach screenshots to the card as necessary displaying the fix
|
|
5.
|
Add the following test result documentations:
* Test Status:
* PR Build:
* Username/Password
* Test case name:
* Environment and devices tested on:
* Test Note.
|
|
6.
|
Push the card to “Testing Complete”
|
|
Mingle Card: 5899 Steps to Reproduce
Expected Result
You are taken to the new static message " This page has been replaced with the Packet Viewer or Sync Events Viewer. Please use these tools instead of this page"
Actual Result
This page below is displayed
!clip-e940-5943.png!{height: 457px; width: 1000px;}
Analysis
Related Cards
5882
Steps for Creating a Defect Card
Test Plan