Naming CI workflows and jobs

[szepeviktor]

Hello!

Here is how CI UI looks like currently.

Excuse me but these names look like expletives without real meaning.
I'd like to improve these names.

Name workflows with a noun and jobs with a verb. For example "Documentation / Publish".

This is from my https://github.com/szepeviktor/byte-level-care repository.

What kind of tests are "CI Tests / Check"? Unit? Functional? End-to-end? Mix of these?

[weiznich]

We are happy to accept a PR that improves this naming.

[szepeviktor]

Could you help me answer my question?

[weiznich]

I think you refer to this as a question:

What kind of tests are "CI Tests / Check"? Unit? Functional? End-to-end? Mix of these?

In that case the answer is: The names don't stop with "CI Tests/Check", but rather continue afterwards. As shown in your image there are the following cases:

• "CI Tests / Check rustfmt style && run clippy" which runs cargo fmt --check and cargo clippy on the project
• "CI Tests / Check sqlite bundled + Sqlite with asan" which checks whether or not the sqlite bundled configuration builds and runs most of the tests there using memory sanitizers (address sanitizer -> asan).

[szepeviktor]

and runs most of the tests there

Yes. I am interested in these tests.
Are these unit, functional or end-to-end tests?

[szepeviktor]

I suspect these are functional test because they include a database back-end (not unit tests) but does not use diesel as in real life (not e2e tests).

[weiznich]

These tests include unit test, integration tests and end 2 end tests. There are several steps involved in this job, which test different things each time.