You already know how essential the QA/QC phase is to any project – without it, you might suffer blows to both your finances and your reputation. That is precisely why we at Valcon take this very seriously and offer only the best of the best engineers to our clients.
Here’s How We Do It
In order to illustrate our services, we figured it would be best to share an example of how our QA/QC teams handled a specific project. Although testing is something that is done on each product/version, it differs from case to case. Hopefully, this text will serve as a good introduction to how things are typically done at Valcon.
What Was the Project?
For this text, we chose to focus on our work with QuickParking, a parking space rental service. Their aim is to provide affordable parking spots in multiple locations near airports throughout all of Europe and the US.
This is something we’ve been working on since the very beginning, three years ago. On top of this being one of our longest-standing projects, we were with QuickParking for all stages of the development lifecycle. The number of people working on it changed from 11-12 to 3-4, depending on the client's needs and the project's phase. Currently, we’re working on maintenance and regular tests.
What We Did
As mentioned, we have been on this project since its conception. However, the focus of this article is the QA/QC side. The team consists of two members, a Manual and Automation Test Engineer. The team size and expertise change depending on the needs and requirements of a specific project, but since we’re now working on just the maintenance, a smaller team is enough to cover all the work.
Typically, QA starts with the testing as soon as developers start with developing. The team works according to agile methodology, so testing is done during each sprint with its peak near the end of the sprint.
For QuickParking, we used several different kinds of tests that are quite common for this kind of project. These are:
- Functional - the purpose is to extensively test each function of the software application by providing appropriate input and verifying the output against defined requirements.
- Smoke, also known as Build Verification or Confidence Testing – to verify that all critical functionalities are working fine, post software build. We opted for this test because it is meant to be quick to execute, and the goal is to provide the assurance that the major features of a system are working as expected.
- End-to-end testing – to verify that software works correctly from the beginning to the end of a particular user flow.
- Unit testing - written and run to make sure that every single method, function, and procedure in the software is working properly.
- Integration testing – to verify that individual modules or services in the software are working correctly.
- Exploratory –to discover, investigate and learn the system.
- Automation / Cypress tests – Automation Testing – performed using special automated testing software tools to execute a test case suite.
- Regression testing – to check if new functionalities or code affect existing features and ensure that the software continues to work as intended. This is an ongoing process that should be done throughout the software development life cycle and ideally automated as much as possible to save time and resources.
Automation was a challenging task in this case – the team had very little time but had a lot of applications that had to be tested in regression. So to shorten the process, the whole team sat and decided what the best approach was and worked out a plan. Tests were written, and a pipeline for automatic start on PROD was done.
After going live with the project, the QA/QC team reported that bugs were found on production by users and by the team. The crucial ones were fixed (hotfixed) immediately after they were discovered.
In conclusion, at Valcon, we are committed to delivering top-quality software solutions to our clients. Our QA/QC phase is an essential part of our development process, and we take great care to ensure that each project is thoroughly tested and meets the highest quality standards.
Through our work with QuickParking, we have illustrated how we approach testing and use various techniques to ensure that the software works as expected. Our approach is based on continuous testing throughout the development lifecycle, ensuring any bugs are detected and fixed immediately.
Overall, our goal is to provide our clients with a high-quality product that meets their needs and exceeds their expectations.
Our team of skilled engineers can help you assess your current software needs, identify areas for improvement, and create a customized plan to achieve your business objectives. With our proven track record and dedication to quality, you can trust that Valcon will deliver the results you need to succeed.
Book a meeting with us today, and let us help you take your business to the next level.