Position: Junior Manual QA Engineer
Category: QA
English level: pre
Years of experience: 0

Using the acquired skills, I tested four games. In this way, it was possible to identify and timely correct all errors that appeared in the projects. Also, thanks to a thorough analysis of the test documentation, I found a lot of inaccuracies in the requirements for the product. As a result, the final product turned out to be 40% more user-friendly.
1. Writing test cases and bug reports on the page
Testing Java tasks
The point was to analyze the behavior of the page and find errors that can spoil the process of use. As a result of the work, several serious errors were found that broke the page.
The capabilities of Microsoft Excel and TestRail were used for work.
2. Documentation testing
In this work, free review techniques were used to prepare for the requirements discussion, all questions, errors, inaccuracies, ambiguities from the requirements were written out, role-based review methods were used to prepare for the requirements discussion, and all potential problems for users were written out.
The program that was used is Microsoft Word
3. Work with the postman
An overview of the analysis of the API documentation of the main postman functions. Creating an environment in the postman. Creating cards on boards in trello with postman. Adding tests to postman queries.
The program that was used is Postman