Cloud Testing Model
Having see a software, cloud is just another beast of software forms. actually we know the golden age of three screen is connected to the cloud. Therefore, we should have a mechanism to evaluate the software that not only work in on-premise but also works in the cloud. The question is “is the cloud testing model is a same beast or different?”
Software testing is a ‘kaizen’ process of the software. In 1950, Deming gave a model called PDCA (Plan, Do, Check, and Act). 60 years after, in one of the international journal I propose the equal model called BUVER (Build, Verify, Revalidate). Frankly speaking, the idea is same how to make the software that we create is fullfilling client satisfication. So whether your software is running in the cloud or just installed in your smartphone, the concept is still the same, the technology and architecture is differents.
Unfortunately there are so many testing models that sometimes overkill. Many jargon such as unit test, whitebox test, blackbox test, defect casual analysis, acceptance test, etc. It just enough to make you lack a sleep and forget your real job is. This post is dedicated to my peers who asks me about how to create a template for software evaluation model
I created a picture to get any engineer to start with their own model.
You can also download the template here
How To Use It
The basic steps are described such as follows.
- selecting your standard (i.e CMM, V&V, TDD) and describe your model so that your document is well known.
- creating evaluation workflow. this step is just like developing an UML activity diagram (or flowcharts) to shows you how to test your software. The mission of this step is to tell the reader how your software fullfill the requirements (functional test) and how your software fullfill the users expectation (Quality of Services, Realibility, Scalability, and any others Traditional software quality concept)
- testing environment. this step like collecting the evidence how you measures your software including your profiling software, your test case, and hardware that are used to evaluate your software.
- Evaluation result. this step show your result into your customer. It is recommended to display it as a table, chart, and side by side comparison. side by side comparison is a good evidence if you want to prove that your software is better than legacy
- Evaluation conclusion. a good engineer is a people who brave enough to tell that his software buggy, lack of feature, and commit to make it better in the future. This section is to show your courage about the truth.
The Fact in Cloud Model
If your software is running in the cloud like using Azure, you can safely skip the hardware part of your evaluation. You should be aware that the hardware is elastic in Azure but the cost is not . Just make sure that you can also evaluate the cost versus benefit in your evaluation workflow.
Software evaluation model is “de-ja-vu” whether you are using mobile, desktop, web, or the cloud. the thoery is still the same. if you want to learn more about software testing I recommend you to read this book