Experiences Flashcards
Tell me about a recent / interesting project you worked on?
Can you describe a challenging project that you worked on and how you handle it?
In the orders portal, I worked on the refund modal. In the refund modal, you can offer refund for the item based on percentages or as a number. Once the user selects a certain refund, let that be either item or shipping fees. The correct amount is reflected based on the applied input and if the user is refunding more than the user had paid for, then an error is shown and the user can not move forward. Once the refund amount is within the purchase price, then the CTA button is enabled and an email of the changes is sent to the customer, the new total is also shown on the bottom of the order.
Tell me about a time you had to resolve a conflict in a team / between you and another coworker?
S: There was a time where the QA’s did not approve of using a new testing tool called Zephyr as we had already logged our test cases and test results in Jira and it was redundant work.
T: I understood the importance of documentation and having an exclusive tool for testing and tracking.
A: I acknowledge both sides, the QA managers and the QA’s. I suggested that we should give it a chance and with that to provide data on the time spent logging the already created test cases in Jira into Zephyr, the quality of the test cases in Zephyr, and the accuracy of the progress of a given sprint.
R: The QA’s agree to the testing the new tool and providing data that we can then submit to the QA managers if the tool was necessary.
Tell me about a time you had to handle a project that was late / tell me about a time you failed?
S: Close to the end of our sprint, we had a couple high priority tickets that needed to go out the next day.
T: I felt the task was easy enough based on the acceptance criteria. It was minor verifications and it was under a settings flag.
A: It turns out that the settings flag did not work and stopped the creation of postage labels. Luckily deploying to staging and automatically running the regression tests caught the error and the deployment pipeline was reverted with the new fix.
R: The defect was resolved by the time it was deployed in production. I realized and learned that even though a setting is behind a deploy flag, we must test with it on and off and also to clarify with the dev the affected areas of the code.
Tell me about a time when you excelled at improving a product / feature with the users in mind?
S: I love findings things to improve on with the users in mind. One of my favorites yet simple ask was to display the type of payment used and the last four digits in a refund modal.
T: I wanted to clarify the specific payment and card used.
A: I suggested to the product manager and designer, that providing the payment info used will showcase the amount refunded to a specific card when using multiple payments.
R: The product manager and designer agreed and have added it into the design specs.
Can you describe a situation where your testing efforts significantly improved product quality? What was the impact?
wip
Tell me about an interesting bug that you found?
Situation: Refund modal, functional testing to make sure that the input that was applied once, twice, three times in the field responses the same results. Applying the value of $20, clear then applying 20 again quickly only took 2 and not the 0.
Task: Took a screen recording of what I was experiencing and sent to the developer if they can reproduce it in dev.
Action: The dev was able to reproduce and identify the bug quickly
Result: The dev was able to fix the bug in the ticket and I was able to apply $20 and clear and re-apply multiple times and got the same results.
Tell a bug lifecycle, process of fixing of the bug?
- New (The bug is identified)
- Assigned (The bug is reviewed by the PM, Lead, QA Lead and assigned to a dev to fix.
- Open (Dev begins working on the bug)
- Ready for QA (The dev finishes the bug)
- Retest / QA (the bug is assigned to a qa team and confirms the bug is fixed)
- Closed (the bug is fixed and the ticket of the bug is closed and resolved)
