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 3 Next »

General advice

  • Allocation for QA Analyst should be always based on project needs, based on our experience it should be about 50% of CE allocation on the project.

  • In case the allocation for QA Analyst is significantly lower than 50% of CE, it is still useful to have QA Analyst on the project, but it needs prioritization of tasks for testing

  • Allocation should be through all Feature Sprints and optionally also through UAT

Typical assignment of QA Analyst

  • Assignment starts just after the beginning of development

  • Test cases are created in test management tool based on real user stories and their descriptions and acceptance criterias

  • Testing during Feature Sprints is mainly focussed on manual functional testing

  • Regression testing is done when new development was done and overall functionality needs to be verified

  • Results of testing are documented in test management tool

  • Examples of functional testing during projects:

    • Created tables and imported data

    • New fields and developed changes in UI

    • Verification of workflows

    • Verification of calculations

    • Correct behaviour for different business roles

    • Project specific tests

How functional testing is processed in Jira

  • When CE finished development of a user story:

    • move the user story to “in review dev“ state - it means the user story is ready for testing on dev partition by QA Analyst

    • assign the user story to QA Analyst

    • eventually also some comment important for testing can be added to the user story

  • When QA Analyst finishes his testing, the following can happen:

    • Test passed

      • Document the test results in test management tool - it should be clear what was tested and on which data

      • Move the user story to “Accepted dev“ status

      • Assign the user story to SA or CE who will deploy the code to qa partition

      • Add a short comment to the user story that the user story was tested and the test passed

    • Test failed

      • Document the test results in test management tool - it should be clear what was tested and on which data

      • Move the user story to “Rejected“ status

      • Assign the user story back to CE who developed the code

      • Describe an issue which was observed during testing in Comments section or in a new Subtask. The following should be clear from the comment:

        • What was tested (including test steps)

        • Expected result and what was really observed

        • Data used for testing

        • Screenshots and videos which could help with understanding of the issue

  • No labels