Anthony Allen Daniel Stefan

My experience as a QA Tester Employee at Electronic Arts was based on the following tasks and responsibilities:
- Attend in daily Meetings, to discuss the day's priorities and assess the number of bugs that required regression testing.

- Occasionally giving feedback to senior members about improvement ideas and optimizing the testing processes.
- Deliver daily sanity checks, smoke tests, and providing progress reports.
- Report the issues encountered throughout the scripted / unscripted testing, performing regression and handling spontaneous requests.

- Assisting engineers with more info about issues to smooth the fixing processes.

- Keeping up to date all the documentation on my project.
A typical day for me at Electronic Arts would begin with a morning stand-up call to discuss the priorities of tasks stated for the day, followed by checking the number of bugs that can be regressed.

Throughout the day, I begin by executing sanity checks, ensuring its proper functionality, followed by regression testing and a smoke checklist. Once the sanity check and smoke test are completed and have not received any new assignment, I proceed with unscripted and scripted testing until a new task is assigned.

At the end of the shift, another meeting occurs to announce the updates and the progress that had been made during the day. When the meeting ends, I was in charge of doing the end of day reports, and ensuring that everyone logs the bugs into Jira conform to the bug quality submission standards, correcting the issues that don't match the criteria and informing the creator of the bug about the mistakes and possible improvements.

Tools that I have been using during my Electronic Arts experience:
- Jira. - database used for reporting bugs, time tracking for tasks and monitoring the current sprint and all the dashboards.
- Test Rail. - Used to execute and create test cases and to create test plans.
- Penguin. - Used to complete A/B tests, campaigns, GDPR, Age Gate, and Account Deletion.
- Confluence. - Used to create and keep up to date all the documentation of the project.

- Charles. A log tool to check the real-time logs of the application.