Guilherme Pereira Freire
About
Detail
Pernambuco, Brazil
Contact Guilherme regarding:
work
Full-time jobs
groups
Networking
Résumé
Jobs
verified_user
0% verified
Quality Assurance EngineerDoubleMar 2025 - Current (1 year 4 months)Improved test runs and user experience: During the implementation of new features in production, a significant number of bugs were reported. My task was to identify the root cause of it and design and implement a robust testing strategy to prevent those bugs. I noticed that the existing test runs were poor, focusing only on happy path scenarios. I proposed and implemented a comprehensive update to the test strategy. This involved: Expanding test coverage to combine happy path scenarios with edge cases and known failure modes. And mapping potential side effects of the new features to identify and test related areas of the system that might be unexpectedly impacted. Identifying the most critical end-to-end test cases and automating them using- QA Automation EngineerFullStack LabsOct 2023 - Current (2 years 9 months)Automated E2E scenarios: There was a lack of E2E coverage and every week QAs needed to run regressions tests manually. So I started automating them using Cypress. Now the coverage is about 80% and now I have time saved and confidence higher in every weekly release.- Shift-left inconsistencies: We had many bugs per Story which was overloading me and the software engineers. So I started asking to run Desk Check before pushing the changes to TEST environment. Also now with the time saved from regressions, I was able to ask and participate with the team in the Refinement meetings. So that we could have a better understanding of the Acceptance Criterias, clearing the ambiguities and doubts. The average number of bugs per Story was 5 and now is a
- Software Quality ConsultantThoughtworksJan 2021 - Dec 2023 (3 years)New suite of E2E automated testing: The team got a legacy system of 20 years without any type of testing. So I needed to build from scratch an E2E automated testing suite using Cypress. By the end of the project, we had robust coverage and felt more confident when delivering new features to the users.- New team members: In that same project we had many new team members that never facilitated any type of meeting. So it was concentrated on a few people. I made up a plan that we were pairing in the meetings to support them to run it. So, after some weeks all team members were rotating and facilitating all types of meetings and the team was feeling more integrated and the communication was happening more easily.
- LSoftware Quality EngineerLiferay PortalJan 2020 - Dec 2021 (2 years)Fewer bugs and a more integrated team: There was a silo where the software engineers were always arguing with QAs regarding if the bugs were legit or not. The team was not used to looking at the test cases created for the stories. So I started presenting the test cases to the engineers before they started coding. After some weeks I didn't need to present the test cases cause the engineers anymore cause they were already looking at them and producing fewer bugs.
- JSoftware Quality JrJoyStreetJan 2013 - Dec 2015 (3 years)New critical features in Production: Some critical new features were being developed for an Educational Platform, and we needed to ensure its quality before release.I planned and executed manual tests for this feature creating detailed test cases covering all possible aspects of the features. I also documented all defects I encountered, collaborating with the development team to reproduce and fix these issues. As a result of that team effort new features were released with a few defects, and we received positive feedback from users.- Agile improvements: The team was having difficult time to keep focus during daily stand-ups and often exceeding the meeting time and deadlines. I was working as a Scrum Master and responsible for facilitating e
- Software Quality JrFastJan 2012 - Dec 2013 (2 years)Complex feature covered by good tests: We needed to deliver a complex feature, and it was important to have clear and concise test cases to ensure high quality to the users. I wrote test cases for this feature using truth table, equivalence partition and boundary values combined with ALTER FACE heuristic. The test cases were easy to understand and follow and covered many scenarios. I also included specific test data and expected results for each test case. The test suite was shared with the whole to ensure alignment with the testing approach. The development team could easily understand and implement the test cases, leading to a faster and more efficient development process.Non-ambiguous features: The system requirements for a new important
- Quality AssuranceOgilvy & MatherJan 2010 - Dec 2012 (3 years)- Starting QA guild: There were no QAs in the team when I first arrived. So I needed to build team consciousness about how QA can benefit their work, understand their perspective and have clear communications on my role and responsibilities. Which made the team deliver better web applications in terms of quality. After that, I also trained 3 new QAs to work on different projects and keep the same quality standards.
Education
verified_user
0% verified
- UB.Sc. Computer ScienceUniversidade Católica de Pernambuco (UNICAP), BrazilJan 2007 - Dec 2012 (6 years)