Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test for BI-2000. Add bad ontology sample. #150

Merged
merged 2 commits into from
Oct 10, 2024
Merged

Conversation

cvacalares
Copy link
Collaborator

Description

Add test for BI-2000.

Testing

Please include a link to a successful run of TAF for this change

Checklist:

  • I have performed a self-review of my own code
  • I have tested my code and ensured it meets the acceptance criteria of the story
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to documentation

@cvacalares cvacalares requested review from a team, HMS17 and mlm483 and removed request for a team September 26, 2024 17:58
And user uploads Ontology "test01-ontology.xls" file
And user selects 'Import' button
When user selects "Confirm" button
Then user can see banner contains "Imported ontology terms have been added"
Copy link
Contributor

Choose a reason for hiding this comment

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

Given the acceptance criteria includes "THEN the user can see the error message disappear when a valid file is uploaded." should there be a "user can see banner does NOT contain 'THEN the user can see the error message disappear when a valid file is uploaded. '" clause?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I have updated to add the "Then user cannot see banner contains "Error(s) detected in file, Bad.xls . (See details below.) Import cannot proceed.".

… detected in file, Bad.xls . (See details below.) Import cannot proceed.".
@HMS17 HMS17 self-requested a review September 30, 2024 16:05
"chromedriver": "^127.0.0",
"chromedriver": "^129.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

Aren't we pinning the chrome version in the GitHub Actions? Do they need to be updated as well?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That I'm not aware. I usually update the package.json.

Copy link
Contributor

Choose a reason for hiding this comment

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

Well, it looks like it ran without any chromedriver issues.

@mlm483 mlm483 self-requested a review October 9, 2024 16:35
@cvacalares cvacalares merged commit 3d94aff into develop Oct 10, 2024
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