Repository navigation
orso test using project workflow - #412
Merged
Merged
Conversation
…ng to decompose it into pieces to apply to other tests)
This was referenced Aug 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the current behaviour (You can also link to an open issue here)?
Solves Re Make ORSO test use the full project stack #398. Current orso validation test validates
abelsSinglefunction only.What kind of change does this PR introduce, does this PR introduce a breaking change?
The test re-implements orso valudation tests using full
RATworkflow which incudes project creation, definition of project parameters and setting all appropriate properties.Other information: