Services/Quality assurance
Quality Assurance
Manual and automated testing that finds problems before your users do. For products we build and for products built by others.
How we test
Two ways of testing. Most products need both, but in different amounts.
Manual testing
A tester walks through the product the way your users will, on the devices they use.
- New features against the requirements
- Old features after every change
- The phones, tablets and browsers your users have
Automated tests
Checks written once and run on every change, so a fix in one place does not quietly break another.
- The scenarios that earn you money: sign-up, payment, order
- API tests that do not depend on the interface
- A run before every release, with a report
Types of testing we do
Nine types. Which of them your product needs depends on what it does and who uses it. We propose the set in the test plan, and you approve it before we start.
Functional testing
Functional testing checks that every feature does what the requirements say. A tester goes through each function with correct and incorrect input and compares the result with the expected one. It covers what users do every day, such as sign-up, search, payment or an order. This is the base of any testing cycle, so the other types build on it.Integration testing
A product is made of parts, such as the app, the back end, the database, payment and mail services. Each of them can work on its own and still fail when they meet. Integration testing therefore checks the places where the parts exchange data. It shows what happens when an outside service answers slowly, answers with an error or does not answer at all.Regression testing
Every change in the code can break something that worked yesterday. Regression testing is a repeated check of the existing features after each fix or new feature. The scenarios that repeat most often are good candidates for automation, because then the check takes minutes, not days. As a result, a release does not bring old defects back.GUI testing
GUI testing checks what the user sees: screens, forms, buttons, menus and messages. The tester compares each screen with the design and then checks that every element responds as it should. It also includes the states that are easy to forget, such as empty lists, long names, error messages and loading. Small visual defects do not stop the product from working, but they are the first thing a user notices.UX / Usability testing
Usability testing asks a different question: is the product easy to use? It checks whether a person can reach the goal without instructions, and how many steps it takes. In particular, the tester looks for the places where users hesitate, make mistakes or give up. A feature can work correctly and still lose customers because nobody finds it.Compatibility testing
Your users have different phones, tablets, browsers and versions of operating systems. Compatibility testing checks that the product works and looks right on all of them. The list of devices and browsers comes from who your users are, so the effort goes where the audience is. It also covers different screen sizes and a slow or unstable connection.Performance testing
Performance testing shows how fast the product responds and how much load it holds. The system is put under the number of users you expect, and then under more, until it starts to slow down. As a result, you see which part gives way first: the code, the database or the servers. It is done before a launch or a marketing campaign, when a failure costs the most.Security testing
Security testing looks for ways to reach data or functions that a person has no right to. In particular, it checks sign-in and password recovery, access rights, the handling of user input and the storage of personal data. The tester then acts as an attacker would and tries the known kinds of attack. Each weak spot is described together with its risk and the way to close it.Localization testing
Localization testing checks the product in every language and region it is sold in. It is more than the translation: dates, numbers, currencies and addresses all change with the country. Translated text is often longer than the original and breaks the layout of buttons and menus. The test also catches lines that were left untranslated.What a testing cycle includes
The same six things on every project, so the result can be checked and repeated.
Want to know what your users will run into?Tell us about the product. We will then propose a test plan and an estimate.
Request testingWe turned to the 24Gen team when the project was in a critical stage. Deadlines were looming, and the product was far from ready. From the very beginning, we were impressed by the team's professionalism and accountability. In a short time, they assembled an MVP, set up scrum processes, and introduced an AI-based solution for moderation. Despite tight deadlines, all key modules were delivered on time and with solid quality. We are very satisfied with the collaboration and confidently recommend 24Gen as a reliable partner for large-scale projects.
Watch the video
Engagement models
Three ways to work with us. We help you pick one on the first call.
Our engineers work as an extension of your team, under your lead or ours.
We agree on the scope, the price and the deadline before the work starts.
You pay for the hours worked and change priorities whenever you need.
From our blog
All articlesCan you test a product you did not build?
Yes. We start from your requirements. If there are none, we describe the expected behaviour ourselves and you approve it.
Manual or automated: which do we need?
Both, in different amounts. Manual testing finds what nobody thought to check, while automated tests guard what must never break. For a young product we start with manual testing and automate the main scenarios once they stop changing.
When should testing start?
As early as the requirements, because a mistake found in a specification costs one conversation. However, the same mistake found after the release costs a fix, a new release and sometimes a customer.
Which devices do you test on?
We propose the list at the start, based on who your users are, and you approve it.
Do you test under load?
Yes. We ask about the expected load, test the system under it before the launch and show you the result.
How do you estimate the cost?
After the first call we break the task into parts and send you a written estimate. When the scope is clear, we fix the price and the deadline. When it is open or likely to change, we work on time and materials or as a dedicated team.
Do you sign an NDA?
Yes, whenever you need one, before we get access to the product.
Tell us about your product
Describe the task in a few lines. We will get back to you to set up a call.
info@24gen.space



