Das ist der Job
Then this will continue a periodic basis for release launches.
Darum lohnt es sich
For example, software team will produce a system of updates in week’s 1 & 2.
TPM will create initial testing packages for QA tester to work through, QA tester may create their own / give feedback for future sprints to cover testing effectiveness.
1/4 of time for Data Input / Validation:
Input – the team has test data that will need to be fed into the ToolSight system to support QA activities, so this would require manipulation, communication amongst the working team, and accessing the dev system to feed data in themselves for specific trials.
Validation – Team member will need to go into ToolSight and periodically explore data that has been ingested, outside of normal QA activities. Responsibilities
1/2 of time for QA Testing:
Working with Technical Product Manager (TPM), work through QA front end testing of ToolSight in support of bi-weekly releases.
Starting in Week 3, QA tester will test the updates (including going back to previous releases/ regression testing) and finish by the EOW week 4. Excel manipulation would be the requirement for this working component.
Cross comparison to other systems will be critical to make sure project is flowing as intended.
¼ of time for Training documentation
Working with TPM, help create and test training effectiveness as the product continues to grow. Be available to he
