Make the test status not set by default

[darmen]

Scope

This PR changes the status behaviour for new implementations of Multi-step API and Browser tests: the status is no longer set as paused by default.

[andrebq]

What happens if we create a test without a status? Will it throw an exception or the test will be created in a undefined state in Datadog?

[arunprakashind]

What happens if we create a test without a status? Will it throw an exception or the test will be created in a undefined state in Datadog?

@andrebq If no status is provided in the test,

1. If test doesn't exist in datadog -> The status would be "Paused" in Datadog
2. If test exists in datadog and is "Live/Paused" -> The same status would be maintained "Live/Paused"

[andrebq]

@andrebq If no status is provided in the test,

1. If test doesn't exist in datadog -> The status would be "Paused" in Datadog
2. If test exists in datadog and is "Live/Paused" -> The status would be maintained "Live/Paused"

If we want to avoid changing something from LIVE to PAUSED (I am assuming this is the reason for not having it set to PAUSED by default), it might be better to throw an exception instead of assuming Datadog will set it to Paused.

Although, I wonder if it makes sense to always revert to PAUSED, given we are potentially changing the test every time this automation runs.

What do you think?

[andrebq]

So, after offline discussion, the outcome is:

• We keep the previous approach of not setting statuses, leaving it for Datadag to decided the actual state
• We will discuss if it is better to have an explict method to select betwee: PAUSED, LIVE, KEEP_CURRENT_OR_PAUSED.