Let's get along: how to simplify life for analyst and QA
Initially, nothing portended problems: we are developing a new integration system in the bank, we have clear and understandable analysis and documentation processes, we have built a full-fledged testing process with a large number of automated tests. Moreover, we regularly interact and review each other's work.
It is not always easy to work together with testers when your system is getting bigger and bigger.
- What to do, when the chosen approach to documenting requirements is not so good now to quickly create new and change existing test cases?
- How to check that new changes are fully covered with test cases without death from getting bored?
- How not to kill each other when you try to find a suitable solution?
In this talk, I will talk about the processes of analysis and testing in our team; about the process problems that we encountered with the growth of the solution; and about the partial automation of the process of interaction with testers, which helped us to solve this problem.
The evolution of the integration system in the internal developer portal
As it often happens a small project with simple tasks grows to a monstrous system with complex logic and a large number of functions. This can also happen with an integration project.
We will talk about the following questions from the analyst point of view:
- What is the REST API?
- How to document it?
- What are you developing: a system with a large number of integrations and internal developer portal?
- Main differences between external and internal developer portal.
Based on this example, I will share our experience in creating an internal portal.