1. O documento apresenta 7 dicas para acelerar os testes de software e entregar resultados efetivos, incluindo: dar foco aos testes mais críticos, antecipar a execução dos testes, versionar todos os artefatos, flexibilizar os ambientes de testes na nuvem, virtualizar serviços e ambientes, automatizar corretamente os testes e testar múltiplas configurações para aplicativos móveis.
Technology will play a critical role in organizations achieving objectives. In fact, in IBM ’s latest CEO study, technology has become the number 1 external factor impacting organizations. Few examples of this…..Cloud speeds service delivery, and so we now see 90% of CIOs view cloud as critical to their plans. We see organizations leveraging mobile to improve reach of services to clients – with 1Bm smart phones and tables shipping in 2012 – a 34% increase in a year. We see over 20B machine centric devices now deployed enabling more responsive business operations and business models. And all of these technologies are generating tremendous data with 2.7 zetabytes of digital content in 2012 – an increase of 50% in one year.
Whatever we are doing is not working
* - Forrestor Study on DevOps, 2011 ** - From a commissioned study conducted by Forrester Consulting on behalf of IBM *** - Need a study Q: What do we see in industry today? A: 41% of organizations experience delays in application installs, 51% of apps rolled back due to production defect, 45% experience delays due to troubleshooting/fine tuning in production. Cycle time – 4-6 weeks to deploy code changes
Step through process begin with let ’ s compare this to the old world. UAT - User Acceptance Testing OAT – Operational Acceptance Testing / Operational Support Testing : operational readiness of a system to be supported.
Step through process begin with let ’ s compare this to the old world.
We always want to be testing. Stub interfacing components out that are unavailable at the time and then re-introduce them when they are available. Continuous integration testing at a “ system ” level. When new components are introduced the automated test suite scan be run as regression tests. Thereby controlling the risk of extra functionality being deployed into the test environment by having mitigated the risk through earlier testing against stubs. This is an incremental and iterative approach to integration testing.
Green == Existing capabilities Orange == New capabilities Dashed border and Italics == No OSLC provider specification but is aspirational