This portion of the space 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. We need to provide the proper context for our target audiences (customer, partner, internal employee, prospect, or someone just perusing our site).

One QA Team for 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.

What we do for our project team

• 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.

What we do for our customer

• 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

• 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)