Automation Experience
I have experience working directly with SDETs and collaborating to establish automation best practices between manual and automation testers. This includes, but is not limited to:
➝ Building, documenting, and enforcing cross-functional team collaboration expectations
➝ Prioritizing automation backlogs based on effort, cost, value, and risk
➝ Determining the level of automation required for features (unit test, integration test, contract test, UI test)
➝ Determining when automation should occur during the SDLC
➝ Automation advocacy with all stakeholders
➝ Automation maintenance and triaging through manual testing and high-level code review
➝ Languages: Groovy, Postman JavaScript, Cucumber
While developing automation is a growth area, I've already started taking courses through Automation Test University. I've already completed a few courses in the Python and Javascript tracks. While I do not have professional automation engineering experience, I have a master's in Software Application Development, helping me quickly learn how to develop automation. As I complete each course, I upload my certificates to my Google Drive, which you can access on the right.
~~Restful Booker~~
Incorporating Automation into the Quality Org
A delicate balance must be met between automation and manual testing. To achieve World-Class quality, both must exist in harmony. This can be accomplished in several ways, but there are many steps to ensure the proper balance.
Benefits
➝ Reduce release time and regression testing time
➝ Expanded testing coverage across compliance, functionality, and security test cases automatically
➝ Reduce time for feedback on code changes
➝ Reduced tech debt and defect count
➝ Utilizes the entire team's expertise for testing: QA, Engineering, Product, Engineering Managers, Business Analysts, Design, Security
➝ Increased sprint velocity
