/
Common SIT sub-sprint

Common SIT sub-sprint

Owned by Jan Kubica
Dec 12, 2024
1 min read

Goals of the sub-sprint

  • Interfaces testing

  • Data quality test

Assumptions

  • Testing is owned and managed by the customer

  • Pricefx team is resolving the bugs and issues that could block the UAT progress

  • No new requirements, no new development!

  • The SIT runs on the QA partition unless agreed differently

Preparation to-dos

Create a separate sprint in Jira (“SIT”). It will gather the bugs detected during the testing

Load “production like” data in terms of the volume and structure. This is important to detect potential corner cases during the testing. The customer will not only test the functionalities of the system, but also the quality of their delivered data.

System Integration Testing

Duration depends on the number of interfaces and volume & complexity of the data. Plan with customer and compare the expected duration with the one in the SOW.

  • Focus on testing all inbound and outbound integrations. 

  • All the interfaces are up and running.

  • The testing instances of the integrated systems are connected or are ready to provide/consume data files.

  • SIT testing, defect logging and defect solving. Please note defects can be on the Pricefx side but also on the side of the customer's systems.

  • Hint: don’t underestimate the capacity of Pricefx team, especially in the first days.

Checklist for the SIT sub-sprint:

  1. Production ready data to be loaded in UAT environment. 
    Control both volume and quality of the data.
    Check both the system performance and data quality.

  2. Team has time to fix found defects.

  3. Client is active, leads testing and communicates via JIRA.