Skip to content

Conversation

@evmiguel
Copy link
Contributor

@evmiguel evmiguel commented Apr 24, 2024

Preview Tests

This PR addresses #1046, providing support for test plans with assertionExceptions that do not have a priority prefix.

The following changes were added:

  • Relaxed regex check on assertionExceptions
  • Util file for setting default assertion priorities

@evmiguel evmiguel requested a review from howard-e April 24, 2024 14:52
Copy link
Contributor

@howard-e howard-e left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@evmiguel looks good! Well done, in also considering a lot of these files are new to you.

How this is done also makes it so that there shouldn't be any additional changes to how the harness files or the aria-at-app handle these assertionExceptions which is great!

at => at.key === key && at.settings === (command.settings || 'defaultMode')
)
) {
const assertionExceptions = setDefaultAssertionExceptionsFromTest(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

setDefaultAssertionPriority seems like a more appropriate name here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@howard-e addressed this in 1373d76

Copy link
Contributor

@howard-e howard-e left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thanks for addressing that last bit of feedback and addressing the issue with the false error being thrown. Great stuff!

@howard-e howard-e requested a review from mcking65 April 24, 2024 20:09
@howard-e
Copy link
Contributor

@mcking65 this PR should now address #1046. So making it possible that instances of valid assertionIds can be listed in *-commands.csv > assertionExceptions without needing a priority prefix. But would instead default to the priority already noted for that assertionId from assertions.csv if applicable.

Could you confirm this works as expected?

# Conflicts:
#	lib/data/process-test-directory/index.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants