10X Testing ROI = 100% + (-50%) + 600% + 85%

ZAPTEST helps Enterprises to achieve testing ROI over 10X! 



Testing is an overhead! However, any organization that drives business digitally can’t afford to release poor quality software. Development-driven testing doesn’t offer quality testing; there are still quality gaps that result in the loss of customers and revenue. Software must be tested by Quality Assurance professionals! The Quality Assurance process needs to allow Enterprises to perform testing just in time and it needs to be cost efficient. 

Traditional software Quality Assurance is the long process. It usually starts with test documentation (manual test cases) development that takes about 30-40% of the overall QA time, than manual test cases are passed to test automation (when used). Test Automation takes another 40-50% of the time. And after all QA teams perform test execution the remaining 10-30% of the time is used.


Traditional QA process is long! It requires multiple people and many man-hours. Specifically, typical test automation technologies that are available for QAs are either API, Image, or HTML-tag based object recognition type and require Application Under Test (AUT) to be present for the automation. Another problem is lack of these tools for cross-platform testing, and therefore it requires development of test artifacts per testing environment that result in multiplication of the test artifacts (development and maintenance) to test given business processes. Also, test execution using these technologies is per platform; that requires each batch of tests to run on the particular testing environment at the time (sequential), and therefore prolongs time for AUT go to market.

All these factors make Quality Assurance of the modern Software Development Life Cycle (SDLC) very expensive!!!

Getting Real about Agile Testing


Chuck Blog Post Photo


I have suspected for some time that Agile Development is bragged about but rarely achieved. I confirmed this at StarEast when I spoke to over 200 testing professionals. Almost without exception, I was told that testing in Agile was being executed two ways:

  • At the end of The Sprint or in reality Mini Waterfall
  • In The Following Sprint or guaranteed production error mode

While this is not surprising, it is cause for alarm. Testing at the end of The Sprint carries all of the coverage issues and time constraints associated with The Waterfall SDLC and adds the compounding negative effects of biweekly or weekly iterative test crunches. The result is poor coverage and QA burnout. As a consequence, applications will suffer quality issues and delays. I can safely say that the QA professionals living under this regimen are miserable. Worse still, application quality is being assured by the developers’ unit testing instead of QA. Let's just give The Fox the Hen House.

Delaying testing until The Following Sprint is a recipe for disaster. In a small shop it guarantees production errors and rework. In Scaled Agile it's much worse. Not only are post release issues guaranteed but also one error can halt the work of multiple teams with shared dependencies. In a large organization with upwards of 50 teams the impact is devastating both in time and cost. In many cases errors are swept under the rug and dumped into production or passed on to The Next Sprint. The result is technical debt and spotty quality at best. This is clearly unsustainable.

Mini Waterfall and Post Sprint Testing are symptoms of relying on antiquated tools. Most of the tools on the market rely on API calls to existing code. This requires QA teams to wait for the code to exist before creating test cases. Theoretically, a test automation scripter could write test cases every time code is checked in but, as we all know, this is rare. Simply put, QA can't afford to wait for the code to be written. With API and DLL dependent tools QA is destined to fail.

QAs - Stop Pleasing Devs, Represent Business!


  • Mission of Quality Assurance in the development process is to assure quality of software based on the application requirements given by the Business
  • Quality Assurance is performed by executing test procedures (Test Cases) based on the application under test (AUT) requirements throughout the given software
  • Test Cases designed by Quality Assurance teams (QA) have to mimic the end-user (human) actions through business processes of the given AUT
  • Quality Assurance has to represent both, the end-user and the Business

Quality Assurance has to control quality of software applications developed by Application Developers (Devs)!

  • QAs have to test applications prior to the applications release
  • Applications have to be tested on multiple platforms and environments (Operating systems, combinations of browsers, native mobile apps, hybrid apps etc.) where the end-users will be accessing those applications
  • Average allocated QA time in the software development process is short, 10%-30% of the SDLC
  • Manual testing is a lengthy initiative, especially considering multiplying test executions per environment
  • IT Executives (Execs) would like for QAs to expedite testing
  • Test Automation allows to speed up test execution

QA testing should be automated!

  • Test automation is the lengthy process (sort of mini software development process)
  • Current test automation technologies (tools) allowscript development based on the existing application GUI (AUT has to exist at the time of test automation)
  • Many QAs are required to support Agile/DevOps with short development cycles (1-2 weeks)
  • QAs don’t have enough time to develop automated testing and to execute it just-in-time (JIT)
  • Execs are losing patience for QAs

QA testing should be performed Just-in-Time!

  • QAs would like to start test automation earlier (before the AUT is created)
  • Many of them are trying to use tools in an alternative way, they are teaming up with Devs to get AUT GUI object parameters (property values) in advance, so they can build test scripts (scripts) before the AUT is created
  • QAs are orienting testing towards Devs objects (not AUT Business requirements)
  • Devs control the QAs

Execs are outsourcing testing leadership to Devs!

  • Devs are leading QAs to test dev requirements (not Business requirements)
  • QA Testing is losing focus
  • Quality of software is jeopardized…  

QAs are pleasing Devs!

QA Team Formation Wins The Game!

ZAPTEST helps enterprises to achieve testing goals either for testing formal way (Waterfall) in COE or Agile in DevOps …


QA Team Formation 2



Organization of the software testing process is the key to productivity of any QA practice in today’s Enterprise. Many organizations are lacking productivity due to the poor organization during consideration of their application development structure, change management and skills of their personnel.


Lack of productivity in testing departments leads to the poor quality of software that result in the loss of company revenues. This leads to companies downsizing and playing it safe by outsourcing their testing to dev teams that are not quality assurance oriented. As a result, enterprises are still NOT achieving desired results in the quality of their software.


One of the keys to successful QA practice is the right organization of testing processes. Like in Football, the right team formations lead to winning the game, QA leaders have to understand what formation of their teams will suit their play the best. There are many different combinations of the team formation, but I’d like to talk about the 2 most fundamental ones.

Don't Write Test Documentation!


ZAPDOC man in chair


ZAPDOC allows QA professionals to create test documentation … with just one click!


Test Documentation development is the essential phase of any Quality Assurance process.  For many Enterprises having test documentation is imperative in order to comply with various regulations. Enterprises are spending approximately 30% of overall time creating new written test cases and maintaining existing ones when application requirements, or test objectives change.


Development and maintenance of test documentation is very time consuming and expensive, an initiative that involves greater headcount in the organization. This is becoming a problem for test automation processes where personnel that create test documentation and where the test automation teams are members of different groups don’t have clear and direct reporting.  Pretty often there are times that test documentation developed with manual testing in mind has to be updated in order to correlate with test automation objectives, and to represent test automation coverage. This correlation discrepancy increases when test automation scripts are being updated due to architectural changes, but test documentation remains unchanged since there is not enough time or it has been lost in the change management communication.

Another problem is ability of QA engineers to support Agile development in DevOps where they usually have fewer resources (one-man-show). QA in DevOps do not have enough time to develop proper test documentation, automate test cases and execute them. Not to mention that Agile development presumes rapid change in the application functionality that has to be reflected in the test coverage. Considering that the test automation is the higher priority, in order to save time, engineers often skip test documentation development altogether.

Page 1 of 10

Contact Us

Tower Place 100

3340 Peachtree Rd NE #1800 

Atlanta, GA 30326 USA

(404) 814-5227