Our testing process
While the bulk of the testing process is done after development, our QA team gets involved at all the major stages of the project — from project planning and design to deployment and post-project support.
- After the project manager has created the project plan, a QA tester is assigned to review and comment on the plan.
- This is done for two main reasons: 1) so the QA tester can already get familiar with the details of the project right from the beginning, enabling a smoother flow when it’s time to fully test the system after development, and 2) so the QA tester can provide inputs about the project specifications from a UX perspective and identify things that need to be addressed early on, before development begins.
- After the project plan is finalized, the design team usually takes over to create mockups of the website, webshop, software, or app.
- Once the mockups are done, a QA tester once again comes in to review the designs and act as a second pair of eyes to identify possible UI/UX issues, and check if the mockups adhere to best practices.
- Once development is done, the system is turned over to the QA team for testing before it is deployed to live. (Read about our development process.)
- The QA tester goes through all pages or sections of the system (on the staging server), primarily focusing on UX and conversions, checking the following aspects: functionalities, UI/UX (for example, if it follows the agreed mockups or the selected template), cross-browser compatibility, and whether the responsive layout is in order on the different devices and screen sizes as agreed.
- For websites and webshops, the QA tester also checks if technical SEO settings and relevant scripts (e.g., Analytics, Search Console, and other marketing-related scripts) are properly in place.
- Any issues found during this phase are reported to and fixed by the development team.
- Once the bugs have been fixed, the QA tester goes through the system again. If everything is confirmed to be in order, the system is presented to the client for user acceptance testing.
- If there are change requests (i.e., new features or minor changes that the client wants to be done, upon seeing the final product), we go through the same development and testing process again before finally switching the system live.
- Once there are no more issues or changes, the system is deployed to live.
- The QA tester does another round of testing once the system is on the live server. This round is quicker and not as intensive as the testing done prior to deployment.
- Using various SEO checking tools, the QA tester gets the site crawled to again check for issues.
- As the system is launched and slowly starts to get user feedback, the client may think of new features or change requests. In such cases, we go through the same process again before the updates are rolled out.
Post-project support and ad hoc projects
- A QA tester can be called in for a project as needed, whether it’s for projects that we develop from scratch, or for projects that we take over the daily maintenance of.
- If you have your own development team and only need a QA tester, we also offer a standalone testing service, where our QA department works alongside your team.
- We also offer a one-time software review service where we offer different review packages (source code review, technical audit, technical SEO and speed audit, and UI/UX review) depending on your requirements. (Read more about our review service.)
Our testing department
1902 Software has a dedicated testing department composed of experienced QA testers who have earned certifications in UX ecommerce.
Our testing is not limited to checking if functionalities are working or if features are aligned with the project specifications — we also make sure to keep an eye on things that affect the user experience, helping you improve your conversion rate.
Having dedicated QA testers ensures that there’s a second set of eyes who checks the system after a developer has updated something or added a new feature. When a system is tested by the same person who developed it, there’s always a risk that the developer becomes nearsighted and overlooks their errors.
Our QA team ensures that these small errors are caught before the customer gets access to the system — a fact often overlooked by software companies.