In this blog series we share interesting cases that we encounter in our daily contacts with test professionals. Sharing practical cases and best practices in the field of software testing contributes to the mission of the Testersuite Team. This mission is aimed at reducing the chance of risks and errors in software by testing smarter, better and easier. This edition is about testing with continuous deployment.
In an interview with a test professional, the increasing dependence on SaaS solutions emerged. This in itself is an interesting development. But it does mean that you have to take a critical look at the way in which SaaS solutions dictate how you set up business processes.
The test professional: If you use cloud solutions, the principle of continuous deployment will only increase. As a customer, you then have to wait and see which functionalities become available when. As a result, you must ensure that you do not just have to change your work process through continuous deployment.
“As a user, we really have to manually test the changed and new functionalities of a cloud application before we use it.”
But continuous deployment involves permanent automated testing? We asked our test profesional. His answer was enlightening: From the developer side, the suppliers, yes. But these are mainly technical tests. As a user, we really have to manually test the changed and new functionalities of a cloud application before we use it.
Agreements with suppliers
So far it was clear to us what the problem of this test professional is. The question that follows is, how do you deal with this as a user (customer) of a SaaS tool? The test professional: As a customer, you will have to make agreements with suppliers. In addition, you must do a good impact analysis when a new version of the SaaS tool arrives. Based on this analysis, it becomes clear which processes are affected and what needs to be tested. It is important to safeguard this way of testing and using new versions within your organization.
How do you guarantee the quality of cloud applications?
The conversation with this test professional brings up a number of things that you should think about when dealing with continuous deployment:
- What requirements do you place on the suppliers regarding the roll-out of new versions?
- How do you organize the lifecycle management of your application landscape?
- Where in the organization is the quality assurance based of cloud applications?
- Who in the organization has the ownership of testing cloud applications?
- What mandate does the cloud application tester have?
- How do you let end users participate in the testing of new functionalities?
What thinks the Testersuite Team?
The opinion of the Testersuite Team is that the use of cloud applications does not release you from manual testing. Not even when there is automated testing such as continuous deployment. Automated testing is an important addition to existing testing activities.
“The use of cloud applications does not release you from manual testing.”
However, automated testing is nothing more than checking what already exists. You check in a stable environment that what is already there, again and again in the same way. Exploratory testing is something else and, as long as there is no artificial intelligence, it will always be a human job. If you want to organize this properly, a test management tool is indispensable.
Experience it yourself with Testersuite FREE
Starting with a test management tool is very easy. Without costs and hassle and within two minutes. Testersuite FREE supports the entire testing process from creating and executing test cases to recording test findings. With a maximum of five users, you can demonstrate in practice the added value of a good test tool. This makes convincing your management a lot easier. From there you can purchase Testersuite PRO or PREMIUM to get started with more colleagues.
Click on the button below and create a Testersuite FREE or PRO environment within two minutes.« back