This site uses cookies according to our privacy policy. If you do not to agree to their use, change your browser settings.
What is the best way to check if a product is user-friendly? Well, this page is about tests, so you can probably guess what we mean. Testing a digital product is one of the best ways to match it with users' expectations. It also allows us to deliver faster and with the use of fewer resources.
Product/market fit adapted to the market needs
Fixed minor bugs
Faster development
Smaller budget needed
Improved user experience
User satisfaction
Business reputation
E2E tests
We use them to check each path that is important to end-users precisely in a way they see those paths. This way, we test the most critical functions such as logging in, payments, adding an event to the calendar, anything that is usually a user’s path in the product.
Unit tests
They let us check the performance of a given piece of code itself, in isolation from the rest of the application.
Integration tests
Using them, we can examine whether individual elements of the application work properly together. For example, we can find out if logging in works correctly with a service that verifies user data in a database.
We have prepared a list of crucial parts in applications that we need to test. It contains login systems, payments, communication with external services and more. A developer's mistakes in features create holes that can be exploited by someone. That is why we havea security review team. It is their job to check the code, look for vulnerabilities, and try to use them.
User tests allow us to check whether the application is intuitive, whether it is easy to navigate and find specific functionalities. It is essential that in this way, we check whether the product we create meets the needs of users, which of its functionalities they like the most, and which in their opinion are not so important.
Thanks to this, we save a lot of time and the client's budget by creating a product that meets the needs of the target group from the very beginning.
If you want to know more about testing, check out our article on internal testing we did on Gorrionki, and our other on testing the app with real users.
It is an imitation of increased traffic in a web application. What would happen if a large number of users wanted to use the application? Or what would happen if someone wanted to launch a DOS (denial of service) attack?
Each time we recommend servers tailored to the needs and budget of our clients so that their product will work as expected.
Charles Macfarlane
Business Development Specialist, Sentience Software
"I've done a lot of remote working before with companies from all over the world. With Gorrion I did not find it to be a..."
Kijafa Crumble
Founder FitnessProLive
"We designed this app by communicating over phone and email, which made it more challenging. But because of their..."
Lean startup MVP – the importance of MVP for startups
It’s no secret that startups are risky. With a limited budget, little time, and initial assumptions, you have to somehow...
CRM, CMS, ERP solutions explained
Today’s world is all about invention. No wonder then that software has become such an essential factor in business. The...
Three.js series – basic tutorial of Three.js
No matter if you are a designer, a developer or just an ordinary Internet user, once in your life you...
