githubbob42 / mingle2github2

0 stars 1 forks source link

i.print is not a function #5103

Open githubbob42 opened 6 years ago

githubbob42 commented 6 years ago

Mingle Card: 5457 Steps to Reproduce

| | |
|-|-|
|**Version #**| |
|**Hardware**| |
|**OS**| |
|**Browser**| |
|**Username**| |
|**Password**|Use LastPass|
|ORG ID| |
|User ID| |
|RayGun Error ID| |

See RayGun Error https://app.raygun.com/crashreporting/pianhu/errors/2268121582#23158595678

Expected Result

What should happen?

Actual Result

What actually happens?

Analysis

There are only a couple of locations where we call the print() function.  The one thing we don’t do is check if the print function exists before calling it.  Add an existence check for print before calling it.

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

I don’t see how we can test this

| | |
|-|-|

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”

   |

   |
githubbob42 commented 6 years ago

Patty : 10/25/2018 14:57 CDT Documented as bug fix in 3/1/2018 Mobile release notes.

githubbob42 commented 6 years ago

Pull Request #2639