Qameta Blog

AI: competitor or assistant?

AI is sure to change our lives forever, but what practical consequences does it have for us as testers today? Let's try to solve some testing-related tasks with ChatGPT! We'll generate and modify test cases, work with automated tests, and more. Hopefully, we'll find out if this is a new tool to make our jobs easier - or if our jobs are becoming obsolete.

Reports create shared contexts for developers

Modern technical problems require T-shaped specialists who know how to communicate across team boundaries. So, how can you boost your communication APIs? Reports are an excellent tool for creating common context - encouraging people to talk to each other.

Shared context vs shielded context: testers and developers writing tests together

This article discusses how developers and testers can collaborate on tests, despite having different approaches. Developers focus on code functionality, while testers prioritize readability and usability, but these differences can be addressed through automation and clear guidelines. Full-stack expertise for testers helps bridge these gaps, ensuring more effective and maintainable tests.

Allure Report is more than a pretty report

The main thing about Allure Report is that it's language- and tool-agnostic thanks to its huge library of integrations and extensibility. Let's journey through our tool's insides and see how it simplifies writing new integrations.

Allure Testops 5.1.0-5.8.1

Allure TestOps 5 is out, and with it, a host of different features to make your life and workflow easier. Significant performance improvements have been made, the visuals have been polished, and the UI has become more consistent and straightforward. We hope you'll appreciate the changes!

Allure TestOps 5 Feature Review: Custom Fields

Allure TestOps 5 is out, and with it, a host of different features to make your life and workflow easier. We'll be going over everything in several articles; this one covers changes to custom fields.

Roots of test smells

Good tests need both test theory, programming knowledge, and understanding of customer needs - so when something goes wrong, the problem is often more deep-seated than just test code. It might be poorly written production code, communication issues within your team, or something even more subtle.

Test smells: cleaning up E2E tests

Clean test code is just as important as clean production code. And knowing how to write isn't enough: you also should know how NOT to write. So let's take some bad JUnit + Selenide tests and try to improve them!

Test smells: cleaning up unit tests

It's important to know best practices for unit tests - and even more so, worst practices! We'll write a simple unit test, show the mistakes people often make with them, and how to correct those mistakes. Hope you'll find it useful!

Allure Testops 4.25.0 - 4.26.0

More good stuff has been added to Testops with the new releases - there are significant improvements to scenarios, copy-pasting, test case formatting, custom fields have been improved, and much more. Dive in to learn more!

Allure Testops 4.24.0

A new version of Allure Testops is out, with quality-of-life improvements for everyone, especially manual testers! Keep reading to learn about real-time collaboration, improvements to scenarios, and detaching automation.

What our tests don't like about our code

Beyond just checking the correctness of our code, tests push us toward writing code that has less coupling and more cohesion. Let's explore the hints our tests give us with a simple weather script.