Skip to main content
Challenging issues you have worked on
Explain each challenging issue you have worked on?
- Issue 01 :
- We are implementing two REST APIs for loading data related to the notes history versions
- Challenge
- Identify how many versions normally a note can have
- Identify how many notes a single patient can have
- What are the most used note types
- How many keywords a single note can have
- What is the length of a single keyword
- How to create that much data within a short period
- Solution
- Need to have information from the customer side
- Ask developers to prepare the SQL queries
- Send the queries to the customer and retrieve the required data
- Based on the data prepare test data
- Issue 02 :
- We had a legal requirement to show deleted notes
- Challenge:
- On which views/modules we are going to show the data
- How do we handle existing data issues like mandatory/non-mandatory issues
- What are the context menu options we are going to implement
- Impact on the customer side since we are loading deleted notes
- How to test if our environments don't have enough data as production
- Solution:
- Send mail to the other module teams about mentioning requirements and changing area
- Gather information about affected areas
- Prepare separate issues to handle existing data
- Inform other teams about the new story and ask for testing support from them
- Report environment creation issue and inform the service desk team to work on it based on the deadline and risk
- Issue 03
- We are implementing a new solution to import data from one environment to another.
- Challenge
- Need to make sure correct data is imported
- Make sure all the data is imported
- Make sure no impact on other data
- Make sure no corrupted data is created
- Solution
- Verify the test data in the early stages, and use Api testing before client-side implementation
- Perform DB verification
- Perform the regression testing
- Perform testing on early-stage
- Do the performance testing
Comments
Post a Comment