My company, at the time, had started a very complicated project with storm topologies, Kafka, events serialized in Avro, and microservices. For this project, I developed a test strategy and also implemented it. All of the components were tested separately and the tests were integrated with Jenkins and run after each build. I also implemented a sanity test to make sure that the extremely fragile infrastructure was still up and running. All of the tests were run nightly as well. The manual tests were stored in JIRA and were referenced in code. On top of everything, we had end-to-end UI test automation that covered most of the features and all of the payloads were generated for every run. The test results were then sent to a Slack channel and to QAconsole.com

The project was very complicated, but I successfully navigated it and built a SaaS solution for a system with DB2 in Docker containers.

For this project, I developed a significant amount of automation for multiple components (a common problem is that you can lose track of all of the results). I first implemented it as a test automation result tool and then decided to add test case management and bug management. There is more work to do but I'm still passionate about further developing new features