githubbob42 / mingle2github2

0 stars 1 forks source link

Blank screens and ***** for certain modified data. #5545

Open githubbob42 opened 5 years ago

githubbob42 commented 5 years ago

Mingle Card: 5906 Steps to Reproduce

| | |
|-|-|
|**Version #**|hunterpeak latest|
|**Hardware**|ipad|
|**OS**|ios 11 |
|**Browser**|safari|
|**Username**|brfield@mobileteam.com|
|**Password**|Use LastPass|
|ORG ID| |
|User ID| |
|RayGun Error ID| |

1. Login from safari on ipad.

2. Open the job J-3B1-A0A-C1FG

3. Change the job name to Travis Test Job Name Change; set the Well from blank to the Diver Down well; change the Primary Job Contact from, blank to a value; set the Projected Start and End Date fields to now.  

4. Go to the sync screen and saw that the upload was in progress.  

5. Go back to Jobs tab and search using the keyword Travis and open that job.  

6. Notice that the lookups have ****** in them now.  not sure why when i had access to select those values from the lookups.

7. Clicked the Tickets tab for that job and then went back to the Job Details tab by clicking the Details folder icon and the center part of the screen is now just blank.

8. Clicked Forms - blank center screen

9. Clicked FX icon.  The browser screen goes white with no more ability to navigate.  

10. Clicked refresh and that got it back on track.   strange.

Expected Result

**** shouldn’t be there when the data and access is correct and FX icon page shouldn’t go white

Actual Result

see script.   See attached.

Analysis

Related Cards

Steps for Creating a Defect Card

| | |
|-|-|

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”

   |

   |