Item group weights, what is it?

Question

1C

Gentlemen, inhabitants of the toaster, I ask for your help) a task came not long ago, in its part the weights of the nomenclature group are mentioned, and that they do not have to be 100, I can’t imagine what the weight of the nomenclature group could mean, there were suggestions that this is some kind of analogue of the "warehouse" but it's not accurate. Please help me with this riddle. It's unlikely that I'll be able to do the full job. There were ideas that the weights are similar to the weights of graphs, and the nomenclature group acts like a tree, but they also say that this is not so.

Answer 1

https://habrahabr.ru/company/piter/blog/337170/

Answer 2

"I want to change the process and add auto-tests and some automation based on TeamCity to make it like this (feature-branches I thought not to use, since we have a lot of small edits, and branches add an overhead):"
That's just the point, that auto -tests without feature branches will not work very well.
More:
Autotests should usually be triggered on a commit. But this also means that the developer does not test the application locally, but simply commits and waits for a response from the autotest.
And if he commits to the master, then one developer can break the build for everyone.
If you use a separate branch for autotest, again, several developers can commit to it and it will not be clear who broke what.
That's why feature branches are used - each developer has created a feature branch like feature/lalala, and autotest responds to a commit to any branch using the feature/* mask
. gitlab, gerrit, bitbucket, where it is convenient to configure the creation of pull requests so that they do not allow merging until there is 1 review and 1 successful build.

Answer 3

Switch to normal TDD to start

Answer 4

We also thought about TeamCity, but after we mastered Bitbucket pipelines, we somehow decided to do without it.
There you can set up automatic (that is, after pushing to a branch, any) or manual deployment (we deploy to Heroku).
That is, your point 6, as I understand it, this is our manual deployment - it is really done with almost one click.