Best tool for automation

Let’s be honest – the test automation domain, at a high level, is relatively simple. We run a linear set of instructions, we have a discrete expected final state, and tests either pass or fail. We generally don’t have broad scaling or concurrency issues, we know all the moving parts ahead of time, and we understand how those parts are supposed to interact. If the harness fails horribly, we can fix it and the end consumer never has to know.Compare to a public-facing application where can consumers can misbehave, load can spike unexpectedly, malware can attack, and problems affect real customers.