Publishing Test Gap

[missymessa]

• This issue is blocking
• This issue is causing unreasonable pain

Add a step in Arcade Validation to do the following:

• Promote using darc's add-build-to-channel the last successful runtime build, using the version of Arcade we're validating.
• Build should be published to the General Testing channel.

[missymessa]

Need to have a broader discussion about how to implement these tests, as changes to publishing are coming.

[missymessa]

Chatting with the Publishing v-team, we identified tests that should cover this:

Tests #1 and #2 will be handled by the Publishing epic, while #3 will be covered by the Validation epic.

1. Arcade-services should have good unit test coverage for darc add-build-to-channel, as we’re depending more and more in this command.
2. Arcade should have tests for the publishing projects. We can’t really exercise the YAML, but we can try and cover the msbuild tasks and proj files.
3. Arcade-validation should exercise the code from the publishing branch of Arcade.

[missymessa]

Going to promote the Arcade Validation build to General Testing to validate this scenario.

[missymessa]

Merged. Closing.