Is software testing a different game of poker?

As per the ISTQB study material, the definition of software testing is "a process of executing a program or application with the intent of finding the software bugs."

But to me, software testing is a different poker game where a tester 'pokes' an application under test using various input actions and data combinations and compares the observed behavior of the application with its expected behavior. The primary dilemma in determining a test strategy is 'how to intelligently poke the application considering limited resources and time?’ To me, this sounds more like an optimization problem.

I have seen many testing teams come up with test cases for an application without giving much attention to the optimization aspect of the problem. Traditionally, the complete set of functionalities of the application under test is broken down into transactions, then into test scenarios and then into test cases with steps and expected results. However, this manual exercise often leads to a big number of repetitions and missed requirements in the test suite created. This is because a structured thought process and an effective optimization technique is usually missing in the process.

If we look at software testing as a special case of the poking game mentioned above, a mathematical optimization problem can be formulated that will generate minimum number of test cases that eliminates all gaps in test coverage.
​
We, at www.testingalgorithms.com, have come up with a process that makes software design process much faster, better and cheaper.