Bugs of the Month: Winter Edition

It’s 2023, and we return with a new entry in our Bugs of the Month series for the latter part of Q4 2022. 

Let’s hope the new year will bring even more bug hunt results to help us deliver functional products.


Project context: An application that runs through Microsoft Teams. It functions as a management system for building companies, starting from the building site and construction size all the way to the complete task percentage and the budget allocated for each task a contractor has to accomplish.

Issue: A new scheduling addition has been added to the project – a calendar page where users can create events. However, this addition offers users several options for setting events: recurring, repeat, gap, and the final date. Our testers have come across a couple of issues when testing these functionalities:

  • Removing the default event start date would cause the application to crash Microsoft Teams completely, as the latter could no longer read the default time value, which would trigger an error;
  • Formatting issues caused by a lack of validation for input fields, allowing the user to input large strings of characters without formatting the data correctly;
  • Another common mistake was caused by the START and END options for an event or calendar entry – the user would be able to set the END date of an event or entry at a point in time before the START of said event, causing the event to not show up in the calendar view. 


Project context: An online platform that allows users to make public profiles displaying achievements for each user individually.

Issue: A client reported a bug encountered in the user’s profile pages: every once in a while, when they were checking their profile or another user’s profile, the data they would see on the page would be data from other users.

The QA team had also noticed that the bug was reproducing to them as well. During the meeting reserved for handling this bug, they noticed that the “wrong” data displayed when someone accessed their user profile would be from one of the profiles belonging to the team members trying to reproduce the bug. While the testers could not reproduce the bug during that call, the new information helped the QA team to continue their investigation.

To reproduce this bug, our testers tried to use two different browser sessions with two different users logged in: User A and User B. When each user visited their profile, our testers managed to call in the data in the same timeframe. They noticed the data returned to the first user would also be returned and displayed to the second user. This problem was caused by a caching mechanism on the CMS side that was malfunctioning, sending the same data to multiple users. The issue occurred when the users requested the same data type in a very short timeframe or simultaneously.

Once our QA team figured out the reproductive steps, they traced the bug in other application sections, eventually receiving a fix during production. 


Project context: A company that helps patients compile data to claim government compensation for their service-related disabilities. The compiling process is done manually by both employees and users.

Issue:  When employees compile user data, they create a profile for the users in one app, each with a unique ‘case ID.’ The veterans open their profiles in another app, make edits if needed, then send them to the government. The former app has an Admin role, which can search for a specific profile using the case ID as a filter. A bug began manifesting, resulting in some case IDs in the employee app not showing results for the Admin in the users’ app. This issue would lead the Admin to believe that the profile in the user app has not been created or even deleted. Our QA team began investigating this by searching case IDs in the employee app as an Admin, using the case ID from the customer app. 

Feel free to share your experience with malfunctioning tools and bugs this month! While you wait, check out our blog, where you can find a lot of information on how to work through QA issues! If you are interested in discussing more, you can book a meeting with one of our professionals. 

Related Articles

Leave a Reply

Back to top button