Improve developer experience

[cbeauchesne]

Issue list

TODO

Build time, Exec time

• build time is too slow
  • #562
    • #1331

Hard to write tests

• #1722
• Hard to know what are the scenario useful for a given feature
  • #1088
• Sugars
  • #1094

Debuggability

• #1696
• #1723

CI ecosystem

• #975
• #1475

Done during Q2-Q3 2023

Build time, Exec time

• #1278
• try to understand why nodejs tracer take 15mn to build (and improve).
• Exec time is too slow
  • #1093 and #1169
  • option to not restart containers ? (need to know what is the time saved with that, and be sure we do not introduce flakyness)

Hard to write tests

• Hard to debug test locally // Hard to write a new test from scratch
  • #958
  • #1084
  • #1123 and #1124
  • #1126 and #1128
• Hard to know what are the scenario useful for a given feature
  • #1086
  • #1087
  • ./run.sh SCENARIO --help. -> print the documentation of scenario

PR process in system tests

• Egg-chicken issue between system tests PR and distant PR
  • #1054
  • #913
  • Communicate about the current recipe
• Decorators merge conflicts hell // Maintenance
  • #1089
• PR review bottleneck -> #1481
• PR without description
• Improve system tests CI
  • #1120

Maintain our CI

• maintenance of scenarios in each CI in each repo
  • #1085 and #1133
• #1210

Other

• Execution en local des N variants

  • N variants. Indeed. Hard to tackle, as one run require mostly all your laptop ressources. Maybe a script that run all variant for a given tracer, but it'll be very slow.

• Importance to follow feature matrix

[anna-git]

Could we run the whole system tests CI without stopping on failure maybe?

[cbeauchesne]

You mean, on the system test CI ?

[cbeauchesne]

@anna-git

Could we run the whole system tests CI without stopping on failure maybe?

FYI, it's done