Member-only story
Make the world a better place by adding ‘End-to-End (via UI) Test Automaton’ in the software contract
It should have always been the case. The word “Engineering” has meanings in other industries, but sadly, not in the software industry.
In a previous article, I listed some news headlines about a big software failure (run by IBM) in my state. The state government dared not to sue IBM for compensation.
Quite the opposite, IBM grabbed a lot more money by delivering a bad system. Clearly, Law-Suit seems not viable, at least in this case. I can understand that state government lawyers are not a match for the big guns that software giants engage in. The escaping causes might have been written skillfully in the contract, before the project started. Basically, they have “Jail-Free Cards”.
Table of Contents:
· How can governments and organizations prevent software disasters?
∘ A Simple and Practical Advice
· How Does it Work in Practice?
· FAQ
∘ 1. Why End-to-End (via UI) Test Automation?
∘ 2. Why Regular Check (every sprint)?
∘ 3. Will this incur more costs?
∘ 4. I think…
