How Does Aetopia Ensure High Quality?

Cillian Marangudakis, our dedicated quality assurance lead, has outlined just a few of the ways Aetopia ensures high quality, every time. 

As an engineer-centric team, technical excellence is at the forefront of every project, software update, and product launch we undertake. Fully committed to an incredible customer experience, we jump through all the hoops to ensure the Aetopia platform is intuitive, helpful, and runs like a dream for every single user. 

We undertake rigorous quality assurance testing.

It’s the role of the software tester to discover bugs and suggest improvements to the system as it nears completion, it’s a stage we take incredibly seriously. This process enables a more effective allocation of time for projects to be completed, as rather than having the software engineers scour the DAM system for potential issues, work is delegated to the software tester, allowing the software engineers to spend more of their time devoted to improving and enhancing the final product for delighted customers. 

We undertake numerous tests on our platform before new launches, but the two primary methods are smoke screen testing and acceptance testing.

Smoke screen testing

Smoke screen testing is one of the most powerful weapons in a software tester’s arsenal. The tester embarks on a process of testing the functionality of multiple builds to determine whether the software is stable. Smoke screen testing often is not enough to determine whether a build is ready for release, but is an important step early on in the process to spot any major stability issues.

Acceptance testing

A software tester can also utilise acceptance testing, which replicates user activity on a system to determine whether it satisfies the customer's requirements. Much more focused on the end goal of the project, acceptance tests ensure that the application fulfils all customer needs and provides a helpful service.  

We know the importance of communication.

There are usually expected issues with builds, and more often than not there are unexpected issues too. It is paramount for a software tester to be able to communicate these issues in a clear, precise and concise way to the software engineers so they can be resolved with little impact on the customer.

Through JIRA tickets and effective conversation between teams we mitigate product issues and quickly solve any which occur post-launch.

The extensive use of JIRA tickets

One way issues are communicated is by the use of JIRA tickets. These tickets are used to highlight problems, or potential problems, so that they can be resolved at an optimal time. It is important for a software tester to be as specific as possible when describing how an issue has been encountered, or how a potential issue can impact the customer's experience.

Thorough conversations between internal teams

As a small, close-knit group of experts, effective communication comes naturally to the whole Aetopia team—it’s why our customer experience is miles ahead of larger offerings in the DAM industry. Issues don’t get passed between departments with lack of accountability, any problems or requests are dealt with straight away by the relevant team.