How to reduce the number of errors after the next improvement of the system?

Question

Project management

Hello
The situation is this: there is a system 1c enterprise.
Programmers, based on the tasks of business analysts, finalize the objects of the 1s system, write new components (new documents, registers, etc.).
They place improvements in the repository and update the test base.
As a result, often, but not always, we get: -
A new revision
- New errors that came along with the revision
How can programmers be adjusted in such a way as to reduce the number of errors in the system that occurred after the new revision? Can any tool or method of work be implemented? Tell me please.

Answer 1

1. Unit tests
   As you understand, there are the most units and to decrease to acceptance

Answer 2

The presence of errors is the absence or defective testing.
Your test base raises questions - why do you need it if it does not protect against errors? Who discovers bugs in the production base, and why don't you give these people the opportunity to see these bugs during the update of the test base?
Depending on budgets and competencies, you can implement some of the scenario testing technologies to automatically detect introduced errors :
1c.ru/news/info.jsp?id=17985
https://habrahabr.ru/post/307808/
//infostart.ru/public/262904/
https://github.com/silverbulleters/vanessa-behavior

Answer 3

There is only one way - hire programmers of higher qualification (well, or finish teaching the existing ones). This is the only way to drastically reduce the number of errors. No tests even come close to giving a comparable result.

Answer 4

as FreeBa already answered above , only more qualified specialists who can competently plan development and do competent refactoring will save you from countless errors
or you pay for tons of testing and bug fixing, or for competent specialists

Answer 5

system 1s enterprise

The Configurator has Configuration Testing, primitive, but there.

Answer 6

Colleagues above have already answered for the most part.
If you work with managed forms, I would advise you to implement the Tester program (test1c.com) in the programming department, completely free, with documentation.