Elliot is a User Acceptance Tester. Read on to find out about his typical day:
User Acceptance Testing is the final part of software development where users test the software to ensure that it is able to carry out the tasks it was designed to solve in real world situations. It is also known as beta or end-user testing.
It is my job to test new software releases to ensure that they functionally work and solve the problem the software was designed to solve. This involves meeting and discussing with various partners to gain an understanding of the problem and how the software developers intended to solve it with software, at this stage I will give recommendations on how other software or competitors resolve similar problems with their software.
Once the Software developers have completed their build the project will come over to myself in the User Acceptance Team who will test all aspects of the software from do all the buttons work to is the code working as intended, I will then feedback any changes to the Software developers and the cycle repeats until the product is ready to be launched. Another aspect of User Acceptance testing is to make decisions about how the software may look or determine how easy it is to use so I will meet with partners to make recommendations.
Within my organisation I also investigate bug reports within the software product, identify what is causing the problem and highlight what the solution should be, this then gets fed back to the software development team who make these fixes.
This job is really flexible but has shifting priorities so being adaptable to change and being able to work on multiple projects at the same time is key I work between 8am and 6pm most days depending on the workload.
Comments
Post a Comment