Synopsis: This is hard to reproduce and have only been able to reproduce it on IOS device. This issue is the user is going and adding Items to a ticket that has19 required items. After he adds those items they do not show on the Items Grid if he runs the report the items appear there if he goes back to the Grid he does not see them if he refreshed the browser or goes completely out of the Grid and then back in the items appear. This becomes an issue because the end users dont thing the item has been added so they re add the item. When they look at the report they see the item multiple times.
Note: Natasha was able to reproduce a similar condition on the release candidate with her user in the test environment for a little bit but then was unable to reproduce it again. What she was seeing is if she deleted items they remained on the screen until she refreshed the Browser.
Email from Customer of how they were able to reproduce it. He thinks this should be easy to reproduce but from our experience it has not been easy.
I’ve been testing with user wel_test@pioneeres.com.fsb and password WELtest4me. I think this should be easy to replicate. What I am seeing is that if you add billable items outside of the required ticket items the ticket item grid isn’t updating and you don’t see these items until you go up to the job and then back into the ticket. What is interesting is that the items while not showing up on the grid do appear on the ticket report. To keep things easy to see I used a quantity of 1 and price override of $100 on each ticket item. In the first screenshot you can see that the ticket item grid has captured 19 billable items (gear icon) yet the ticket total is showing $2,200 for all 22 billable items.
!Pioneer_imiage_1.png!
!Pioneer_imiage_2.png!
!Pioneer_imiage_3.png!
Here is the grid after I went up to the job and then back into the ticket item grid. You can see Depthomoter, Fishing Tool, and Fishing Tool Rental ticket items.
!Pioneer_imiage_4.png!
Here below you can see when I select all the billable items we are seeing 22.
!Pioneer_imiage_5.png!
Do this
Then do that
Followed by this
Expected Result
What should happen?
Actual Result
What actually happens?
Analysis
YM – symptoms observed while debugging when this situation occurs:
user tries to select items and delete
ticket/items/list – TicketItemsList.prototype.handleTicketItemRemovedFromTicket tries to execute, but dies because ‘this.source’ is undefined
this.__hasDeactivated is true in this scenario
it looks like for whatever reason the ticket item list viewmodel never successfully deactivated
moving back out to jobs and entering any other ticket results in the same issue
it’s almost as if the ticket item list viewmodel is perpetually getting reused in its broken state regardless of the ticket being viewed
reloading the browser fixes this (not helpful)
Related Cards
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: 5915 Steps to Reproduce
Synopsis: This is hard to reproduce and have only been able to reproduce it on IOS device. This issue is the user is going and adding Items to a ticket that has19 required items. After he adds those items they do not show on the Items Grid if he runs the report the items appear there if he goes back to the Grid he does not see them if he refreshed the browser or goes completely out of the Grid and then back in the items appear. This becomes an issue because the end users dont thing the item has been added so they re add the item. When they look at the report they see the item multiple times.
Note: Natasha was able to reproduce a similar condition on the release candidate with her user in the test environment for a little bit but then was unable to reproduce it again. What she was seeing is if she deleted items they remained on the screen until she refreshed the Browser.
Email from Customer of how they were able to reproduce it. He thinks this should be easy to reproduce but from our experience it has not been easy.
I’ve been testing with user wel_test@pioneeres.com.fsb and password WELtest4me. I think this should be easy to replicate. What I am seeing is that if you add billable items outside of the required ticket items the ticket item grid isn’t updating and you don’t see these items until you go up to the job and then back into the ticket. What is interesting is that the items while not showing up on the grid do appear on the ticket report. To keep things easy to see I used a quantity of 1 and price override of $100 on each ticket item. In the first screenshot you can see that the ticket item grid has captured 19 billable items (gear icon) yet the ticket total is showing $2,200 for all 22 billable items.
!Pioneer_imiage_1.png!
!Pioneer_imiage_2.png!
!Pioneer_imiage_3.png!
Here is the grid after I went up to the job and then back into the ticket item grid. You can see Depthomoter, Fishing Tool, and Fishing Tool Rental ticket items.
!Pioneer_imiage_4.png!
Here below you can see when I select all the billable items we are seeing 22.
!Pioneer_imiage_5.png!
Expected Result
What should happen?
Actual Result
What actually happens?
Analysis
YM – symptoms observed while debugging when this situation occurs:
Related Cards
Test Plan