search

githubbob42 / mingle2github2

0 stars 1 forks source link

Audit Log shows UploadComplete with no errors, but the sync packet shows errors for events against deleted records #5240

Open githubbob42 opened 6 years ago

githubbob42 commented 6 years ago

Mingle Card: 5597 Steps to Reproduce

| | |
|-|-|
|**Version #**|4.0.1.3978|
|**Hardware**|iPad    |
|**OS**|iOS 11.2.5|
|**Browser**|Safari|
|**Username**|rmabry@capstonefire.com|
|**Password**|Use LastPass|
|ORG ID|00D41000001Mhom|
|User ID|00541000003BcjwAAC|
|RayGun Error ID| |

```Please see Capstone production org Audit logs: AL-31917/AL-31918, AL-31923/AL-31924.

Expected Result
---------------

_When an event errors in a sync packet, the Audit Log header info should list an error message._

Actual Result
-------------

_Sync packet shows events that errored due to deleted record, but Audit Log header info lists no error messages. see attached screenshots._

_Analysis_
----------

_AL-31923 and AL-31917 do show there are some deleted records.   But those could have easily been deleted after the events were successfully applied.   The messages are not errors, they are simply indicators to the status of the record the event indicates._

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”

|

|

githubbob42 commented 6 years ago

Patty : 10/26/2018 07:32 CDT Documented as Performance Enhancement in 3/29/2018 Mobile release notes.