[Security Solution] Support for running Cypress e2e tests under different licenses

[banderror]

Summary

We need to be able to test at the e2e level (Cypress tests) certain features or bugfixes that depend on the current license, for example:

• [Security Solution] Disable ML rule's edit button link under basic license #143260
• [Security Solution] Fix rule details enable/disable toggle isDisabled state #143252
• [Security Solution] The ML rule link for the license upgrade is different from the one under cases tab #137148

Currently, we have support for different licenses in our API integration tests. Some are run under the Basic license, and some under the Trial one. But we don't have support for that in the Cypress tests.

Let's add this support. We can start with some research and building a PoC and later we can create more concrete tickets if needed.

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[MadameSheema]

@banderror I did a research on this topic before with Threat Hunting team because they wanted to have some licensing tests on Cypress as well, they end up testing the behaviour on a different layer, so nothing was finally implemented. Here I'll try to list all my findings and useful information we need to take into consideration:

• Our Cypress tests are executed on top of FTR.
• By default when executing Cypress we are using the Trial license
• Licenses work per instance
• Once you change the Trial license you cannot return to that one.
• Here is an example of how other teams are dealing with licensing in a different testing layer.

Taking into account all the above, at first glance, there are two solutions we can implement:

1. Change the license each time that is required for a test.
2. To have different cypress configurations, one per each license type.

Personally, I'm in favor of the second option, I'm not a fan of the first one because:

• If for whatever reason the license is not correctly updated, other tests are prone to fail increasing flakiness and false failures.
• We need to have the licenses hardcoded on the code, meaning we need to manually maintain the licenses.

Happy to provide a solution for this if needed or to help with the implementation.

[banderror]

I need to think about that @MadameSheema, thank you so much for sharing this info!