Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

It is expected that partners will have their own QA Analysts in the project team, but this does not mean we do not offer support. We can help especially in these areas:

Project start meeting

→ during planning or at the beginning of Feature Sprints

  • clarify expectations from testing

  • discussion about responsibilities during Feature Sprints and during UAT

  • check that Partner is ready for testing on the project

  • clarify potential risks so Partner knows about what can happen when testing is not done

  • expectation from test management tool usage

Beginning of the project

  • clarify expectations from QA Analyst

    • tools and methodology

    • UAT phase and project ending

    • testing by customer

    • potential risks

  • sharing our project experiences

    • typical issues during projects

    • importance of testing

    • tips for smooth projects

  • tips for QA (Beginning of the project )

    • allocation

    • cooperation with other roles and with the customer

    • expectations during project phases

  • test management (Test Management Guidance )

    • tool selection

    • test cases

    • bug reporting

    • sharing test management with customer during UAT

  • test automation (Test Automation )

    • demo of Cypress

    • tips for usage

  • communication with customer

  • No labels