Our Quality Assurance team work to one simple guiding principle, “If it isn’t tested, it doesn’t work”. We hold the belief that any solution is only as good as the level of testing it has been put through. Our reputation is built on providing beautiful software that is intuitive and simple to use- we can only provide this through continuous, unbiased testing of all features within a solution.
Testing helps us:
Due to the variety of products, services and technologies delivered by cloudThing, each project requires a bespoke approach to ensure effective testing. We have seven principles around our testing approach to ensure consistent quality:
Before any Test Execution takes place, it is important to plan the test strategy to ensure all stakeholders agree on how the testing will be deemed a pass or fail. We do this by performing detailed risk analysis to formulate a detailed plan of what the potential impact of not testing this feature would be, then working back from there to prevent any of these impacts from occurring. The risks we look at include the financial, reputation, security, data protection, operational, regulatory and technical complexity.
Once we have analysed the risk, a comprehensive test strategy is outlined detailing the testing methods. This could include automation, end-to-end testing, exploratory testing and more.
Once the 'what' and the 'how' have been defined, justified, and agreed, the Test Execution Stage puts that theory into practice and we test to the same Agile model as any other stage of Development. Test Cases will be written, reviewed and executed, and progress will be monitored and controlled through the usual cloudThing project management processes. This enforces total transparency and collaboration between the QA team and the Developers which means that customers are in complete control and are welcome join the same SCRUM calls to hear testing results, as is expected from cloudThing.
Testing is monitored, controlled and has the same entry/exit criteria as any other stage in Development. Wherever possible, testing takes place concurrently within the active development sprint. This is to ensure as many user stories are delivered to the customer that are certified as ‘working’ by the QA team. Any defects found during testing, are given a priority and severity rating which reflects that of our DevOps department – this ensures that the appropriate time and resource can ensure the defect is fixed quickly and effectively, before the feature is retested.