Be able to schedule atomic testing and follow result over time for detection rule e2e testing

[SamuelHassine]

Use case

Be able to schedule atomic testing and follow result over time for detection rule e2e testing

@jborozco @Jipegien to be prioritized (already discussed).

[EllynBsc]

Hi @SamuelHassine 👋

1. To clarify why we need to implement the scheduling for atomic testing :

I'm not sure I understand the need here as we can: -create a simulation with an inject and quickly test it -create a scenario with an inject and schedule it in a recurring way

2. We don't have e2e testing yet and we just started working on the first chunk of unit tests for the simulation scope. Would unit testing be enough for the scope of this feature to start with ?

cc @jborozco

[SamuelHassine]

Atomic testing is the first use case for end to end detection testing, without creating simulation / scenarios associated to it.

We cannot force the user that just would like to test 1 payload every 2 hours to go through the creation of a simulation just for this.

[EllynBsc]

Thank you @SamuelHassine. After discussion with @RomuDeuxfois, I realized I just got confused by the semantic of e2e:

• e2e on OpenBAS for us -> tests (unit tests, end to end)
• e2e on OpenBAS for users -> test security tools

Sorry about this confusion 🙏