Challenges

The Client had challenges implementing a robust solution for date-time testing.

They needed to do this for multiple business units and time zones throughout the globe.

Solutions

Qualitest helped create a matrix solution that was easy to understand.

The matrix solution created also covered all scenarios for different business units for the Client.

Results

The solution provided helped the development team as well as the testing team to implement the new matrix flawlessly.

Training was also deployed to all team members to implement the same solution throughout all the Client’s product lines.

Client overview

Our Client is a leading global provider of advanced analytics, technology solutions, and clinical research services to the life sciences industry. They create intelligent connections across all aspects of healthcare through its analytics, transformative technology, big data resources and extensive domain expertise.

Their Connected Intelligence product delivers powerful insights with speed and agility — enabling customers to accelerate the clinical development and commercialization of innovative medical treatments that improve healthcare outcomes for patients. They conduct business in more than 100 countries worldwide.

Fixing application challenges with global time zones for date-time implementation

The Client started to implement date time logic in their applications, but their initial draft was not able to give a proper solution to their business challenges. They continued to face issues when fetching intakes from different time zones, and in this process our Client was not able to get all the intake needed to process a single date according to geographical location. They tried to change their initial draft to implement it with the logic that while saving any intake in their database system, it should also convert the date and time of incidents to midnight then convert this time to GMT according to the user’s business unit and save the record accordingly.

While fetching the date the approach was to subtract/add time according to the user’s local time zone, then create a search window of calculated time +12hr and -14hrs, and fetch all the records falling under this window. The development team was unable to achieve the expected results with this methodology, and the testing team was also struggling because the globe was divided into many local time zones.

The time paradox: identifying geolocations to cover all time zones globally

When Qualitest began working with our Client as a testing support team member, this implementation logic was assigned to us to test. A solution was designed to test the implementation with one person rather than four people to provide maximum coverage in one go. This was a cost saving solution for the Client.

Qualitest found and implemented a solution which is part of Salesforce service cloud to divide the world into business units and then based on the GMT time of those units created extreme time zone users along with local time zone users. Out of 4 layers of Salesforce application (Compute, Salesforce UI, Snowflake DB and Mulesoft), we were responsible for the implementation on Salesforce UI, as well as on Snowflake DB.

Phase 1 – identification of geolocations to cover all time zones

Examples of extreme time zone users:

  • A Midway Island, Samoa user
  • A Line island user

Examples of normal business unit users:

  • A European BU user
  • A US BU user
  • A Japanese BU user

Phase 2 – create test scenarios and test data to cover all expectations

In this phase, Qualitest designed these scenarios with relative test data to cover the logic:

  1. Test with Same BU and Local time zone – US
  2. Test with different BU and Local time zones – Japan
  3. Test with different BU and Extreme time zones for Midway user
  4. Test with different BU and Extreme time zone for Line Island user
  5. Test with Same BU = Local time zone – GMT – EU

By using this approach, we were able to mitigate the risk of covering logic implementation in all aspects. The test data was based on the internal implementation of the logic as well as user acceptance.

The phases involved in testing:

  • Test Planning: this included goals and constraints for hits per minute, throughput, response times, resource allocation and any other success criteria identified by the Client.
  • Prepared Test Environment: IVP lighting DEVB environment.
  • Test Scripting: created a test script based on user identification and user test data related to the logic.
  • Executed and Analysed: execution of scenarios and finding defects, then discussing those defects with development team to help them understand the exact root cause of failures.
  • Re-executions: providing a base of debugging and fixing any defects and re-execution as we implemented regression to ensure the expected outcome.
  • Test Report: prepared a final detailed test report containing executed scenarios, test data and the actual testing results.

Key benefits

  • By using this approach our Client achieved their target with only one engineer rather than using three, thus saving on their resources.
  • Qualitest was able to find nine defects in the early stages of system testing and three defects in integration. This helped our Client fix these defects quickly.
  • Through the use of proper coverage and effective test data the actual defects were identified and the development team was able to understand the root cause of those defects.
  • The Client was able to demo this solution successfully to show how it could be implemented across different time zones. For this a custom UI was created which is connected to the Service Cloud and the flow tested accordingly.
quality engineering free assessment