In March 2016, Googler Ari Shamash discussed in an article titled “From QA to Engineering Productivity“, on how Google Testing teams were grouped to contribute towards improving overall software engineering efficiency and productivity.
Much inspired, my project team tried to emulate some of the practices and processes recommended by Ari on the large-scale test automation project that we were involved during that time. However, we couldn’t succeed, mainly because the teams were working in silos. In addition to that, the engagement had multiple vendors and it became even more challenging as priorities kept changing.
Therefore, at Zuci, we didn’t want to build standard test automation frameworks that can be used by test automation experts alone, instead we wanted to design a tool that has something for everyone involved in building the software.
And, the answer was … EPIQUE (Engineering Productivity Improvements with Quality Engineering).
So, what exactly is EPIQUE? Is it completely different from other test automation frameworks? How does EPIQUE contribute to Engineering Productivity? What has EPIQUE got to offer for functional analysts and business users?
We hear your questions!
Here’s a quick peek into EPIQUE and its features.
- It is integrated with “SHABD”, (voice based solution) that helps business users design UAT and to create voice-based mindmaps
- It has a feature to measure code “daily” (run all tests) and “per-commit”(run only tests affected by the commit)
- It enables testers to update test results to any test management tool using voice API’s ZUBOT (AI powered smart BOT helps Dev, Test and DevOps team in optimal use of infrastructure)
- Test Automation Engine built using Selenium and Java
- Other standard test automation framework features such as dashboards, reporting etcetera
Our clients think it’s awesome!
What about you?