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

QA Analyst should be typically focussed on these tasks:

  • manual functional testing based on project user stories

    • prioritize your tests so you can help the project the most - typically positive cases should be the first ones

    • be aware of your project allocation - if your allocation is not big enough, discuss it with your PM

    • keep in mind that it is not possible to test everything so start with the most important tests

  • reporting of your work

    • use X-Ray for test management - it must be clear what you tested and what was the results

    • use “light version” of test management - you don’t have to document every test step, simple description of what you will test is enough

    • when you find an issue, don’t forget to change the status of the user story to “rejected“ and assign user story back to CE

  • reporting of your time

    • reporting should be done every day

    • time should be reported to the correct user story or to administration task

in case your allocation is big enough on the project, you can add also the following tasks to your list:

  • test automation for internal purpose to support development

  • regression testing when the project is close to the end

  • smoke testing on qa partition before the customer starts testing

  • more manual functional testing - more calculations, more variants of products, different data

  • API testing or other testing based on project needs

  • No labels