we have new release with new features each 2 month. and canary release each 2 weeks. there are ways to put something new not breaking everything around. because if you do, not only your costs for testing will increase but also your costs for development, planning, documentation. and those costs will be much more serious. I dont know how you can explain to your customer something like "ok, you want to add some new feature, so we also have to rewrite all other features. it will cost all that you already spent and little more."

and also if you change all around you have to test it with full cover

then of course you will need manual testing because automation is only foe regression

не даю

Learn any PL , api, theory and go

Thanks. 🤝

sorry WAT? which new feature you mean? to break down all your test is fully enough just to change a design theme cause everything in web-ui is closely connected with finite web page structure.
And I don't know if you read a scrum guide for example where was outlined "release of any feature as frequently as every week" (and that isn't a maximum frequence)
Also just bug fixing can break down all selenium tests

seems as no one from local testers has experience with working on b2b products...

but at lest it would be useful not only learn newest and more newest frameworks methods and tools it attempts to seem as real developer bgg - but at least read or listen someones who has real hands-on experience in QA such as Rex Black

Решил почитать про API,что это зверь такой. ))

Стиль разработки?

Ну вот и пытаюсь разобраться.

contract, oh my ass...