Achieve customer satisfaction by identifying software issues before your product is released
Reduce the risk of product failure in the production environment
Ensure lower maintenance costs
Team meeting—we call it Quality Kickoff, which is a process meant to unify quality practices among Polidea’s projects and use the best of them.
Test process analysis—here, we identify test conditions, set up required test infrastructure and tools, design the tests, automation scope, strategy, and the plan.
Test implementation and execution —we then take test conditions into test cases and suites, and execute them, following the procedures.
Test automation scripts—we are developing them according to the plan, using the best programming practices and patterns.
Test reporting—an essential part of the testing process. In this step test reports are generated and provided automatically by the testing tools or by our developers.
"Testing is an essential yet often underestimated part of the web development process, that is crucial for the success of your web development project. Clients usually feel like spending time on writing automated tests is a waste of time, however fixing a problem later will cost you way more."
Lead Software Engineer,
HER impact is helping female entrepreneurs scale their businesses with a dedicated platform. Our testing team was responsible for the maintenance of the testing process, the performance of the front end and back end functional testing. In the Cypress automation tool, we set up an automation infrastructure and created end-to-end tests. Moreover, our team prepared and conducted crowd testing sessions. Throughout the project, we held bug scrubs and acceptance meetings to ensure the success of the project.
Humon Hex is a wearable device designed for athletes that measures the level of oxygen in blood cells using LED light. Polidea delivered iOS and Android apps using React Native technology. We then integrated them with the Humo Hex ecosystem of interconnected devices (Humon Hex sensors and the cloud) via Bluetooth Low Energy.
EFL is a pioneer in psychometric and alternative credit scoring. They wanted an app that would apply their revolutionary algorithms to analyze a borrower’s attitudes and beliefs to better assess the risk of the unbanked or underbanked in less developed countries. Our team delivered UX/UI design and implemented the software into a native Android mobile app, along with a responsive web app.
We got the answers!
Do I need to test my web application?
Yes. There’s no such thing as a bug-free development process—catching and fixing those issues in the early stage of the project saves you a lot of money later on, when the product is released to the market. Thanks to an experienced team of testers, you can check how your web app is behaving on different devices and browsers. Testers also verify if all the functions mentioned in the requirements are implemented (functional requirements) and test the look & feel of your application, e.g. how fast does it load, does it work as intended (non-functional requirements).
How to test responsive web design?
Responsive web design is a way to craft apps to provide an optimal viewing experience. Testers focus on making your app display perfectly on different screens, browsers, and mobile devices.
What are the steps of web testing?
A standard testing process consists of the test process analysis, test implementation and execution, test automation scripts, and test reporting. What’s unique about our approach to testing is that we start with the Quality Kickoff—our process meant to unify quality practices among Polidea’s projects and use the best ones.
What are the costs of fixing the problems at each stage of the development process?
It’s hard to estimate the exact numbers, as each project is different. Generally, it’s the cheapest to fix issues in the earliest stages of the development (requirements, design), and way more expensive when the app reaches the acceptance tests. However, the prices skyrocket once the product is released to the market (see the graph below).
When should I hire a web development team? It’s an approach that encourages starting testing as early as possible in the development process. Thanks to that, defects are found earlier, even before the implementation of a feature begins.
We always want to provide products of the best quality, but we’ve encountered some problems on our way. Quality practices in our projects differed with the experience of our team members.
That’s why we’ve started and implemented our process that helps us assure the quality in our projects—and we named it Quality Kickoff.
At Polidea, we value workshops and love to participate in them. Therefore we had several brainstorming sessions, which resulted in the conclusion that quality assurance (as a part of our DNA) must be consistent with one of the other values—agility.
The main goal of the Quality Kickoff is to use the best quality practices in every project, smartly and reasonably. How? By creating and maintaining a knowledge base of these practices and mistakes to avoid and providing a process that helps the team implement them. The other value is constant discussion about the quality that the process inspires.
We’ve designed the Quality Kickoff process as a simple and straightforward framework—we treat quality practices as an integral part of a project since the beginning. Quality Kickoff is triggered by the first meeting, in which the team plans future quality processes and tools based on experience gathered from previous projects.