QA Team Support

The QA Team Support in the Pricefx environment plays a crucial role in ensuring the quality and functionality of the pricing solution. They work closely with the project team to identify and address any issues or risks during the development phase. They also assist the customer in achieving their functional objectives and quality expectations by providing guidance in key testing activities. The QA team performs various types of testing, including functional, regression, and smoke testing, while the customer is responsible for user acceptance testing and end-to-end testing. Additionally, the article mentions that performance testing and security testing are add-on services currently in development.

This article should provide a good understanding of this role, product, module, or Pricefx component. We should strive to explain how this knowledge component fits into the Pricefx environment and the purpose that it serves.

One QA Team, Many Customers

We help our project team to find all important issues and risks in the development phase, before UAT and be sure we successfully met customer requirements. We help our customer to get the pricing solution according to his requirements.

Supporting our Project teams

The QA Team Support in the Pricefx environment ensures that the solution meets the customer's functional objectives and quality expectations, these are our core areas of assistance:

  • Help to ensure the Solution meets the Customer’s functional objectives and quality expectations.

  • Perform functional and regression testing taking into account a holistic view of the Solution, not only specific user stories.

  • Create a test plan, test cases, and test report for the areas of testing where Pricefx is responsible. Works closely with the Project Manager to ensure key inputs and prerequisites are met in advance of key testing milestones.

Supporting Customers

We help ensure that the solution meets the customer's functional objectives and quality expectations. We identify and address defects before key user testing, such as User Acceptance Testing via these core areas of assistance:

  • Help ensure the Solution meets the Customer’s functional objectives and quality expectations.

  • Identify and address defects ahead of key user testing e.g., User Acceptance Testing

  • Provide limited guidance across key testing activities performed by Customer team members e.g., User Acceptance Testing to help Customers run successful tests

Footnotes

Additional areas of assistance provided by the QA team include unit testing, functional testing, regression testing, smoke testing, end-to-end testing, UAT testing, and providing limited guidance for key testing activities performed by the customer team members.

  • Unit testing: Unit testing is focussed on the smallest units of the software (like classes, methods that are created during programming the solution). Unit tests are always the responsibility of Configuration Engineers

  • QA testing (Performed by QA Analysts according to Pfx standard methodology):

    • Functional testing: Single user story or multiple user stories from a functional point of view

    • Regression testing: Checking that an update to one user story doesn’t break other user stories (functionality)

    • Smoke testing: a small subset of regression tests to be sure the solution is working after deploying to a new partition

  • End-to-End testing: Pfx functionality with CRM / ERP (upstream/downstream) systems. Customer responsibility

  • UAT testing: Customer responsibility

  • Performance testing: Add on service by Pfx (in development)

  • Security testing: Add on service by Pfx (in development)

 

 

Â