Traditional test automation was built so that it was needed to write scripts and lines of code to design and execute a test case. This means that the testers were required to have good coding skills. The technical skill level of human resource should be high enough to write robust testing code.

Scripting and coding have forced Business analysts and SMEs to stay away from test automation due to its complex requirement of programming skills, creating a gap between Business and IT, domain expertise and technical automation knowledge.

The more time your people spend on coding, the less time they spend testing! The primary job of the testing team has moved from testing the functionality of the application to technical development and implementation of scripts, leading to low levels of test coverage and poor software quality.

In traditional QA methods, the scripts are developed only after the application is built and stabilized, so any defects found at that stage are 10x times more expensive to fix.

Scripting itself leads to more complexity and a higher cost to maintain the scripts. The expenses incurred in maintaining these scripts erode the advantages that automation can bring.

On the other hand, scriptless testing can eliminate the need for any prior scripting. This allows testers to focus on testing activities rather than putting a lot of effort into creating test scripts and maintaining them for each change.