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

[Feature]: Instructions to verify behavior and Tests #108

Closed
1 task done
wincowgerDEV opened this issue Feb 13, 2023 · 9 comments
Closed
1 task done

[Feature]: Instructions to verify behavior and Tests #108

wincowgerDEV opened this issue Feb 13, 2023 · 9 comments
Assignees
Labels
enhancement New feature or request reviewer comment feedback from manuscript reviewers, should be prioritized

Comments

@wincowgerDEV
Copy link
Collaborator

Guidelines

  • I agree to follow this project's Contributing Guidelines.

Description

There doesn't seem to be any automated tests. While the desired behavior here is relatively clear/trivial, there's no formal instructions to verify behavior.

Problem

NO

Proposed Solution

Need to add formal instructions to verify behavior and add clarity on the automated tests currently implemented.

Alternatives Considered

NA

@wincowgerDEV wincowgerDEV added the enhancement New feature or request label Feb 13, 2023
@epierotti3 epierotti3 moved this to Needs Review in TrashAI Feb 14, 2023
@epierotti3 epierotti3 moved this from Issue Approval to Icebox in TrashAI May 11, 2023
@wincowgerDEV wincowgerDEV added bug Something isn't working reviewer comment feedback from manuscript reviewers, should be prioritized and removed bug Something isn't working labels May 16, 2023
@wincowgerDEV
Copy link
Collaborator Author

@shollingsworth is it trivial to write some instructions to verify the automated tests? Another thing I could probably do instead is just make a test set and then make a video explaining how someone could use it to verify behavior.

@wincowgerDEV
Copy link
Collaborator Author

Perhaps adding this is actually enough: #124

If we add that to the downloads and then I explain how to use the schema validator tool like https://www.jsonschemavalidator.net/ in the updated video then that should be proof enough that the pipeline is working as expected to create a data output useful for users.

@epierotti3 epierotti3 moved this from Icebox to To-Do in TrashAI May 18, 2023
@epierotti3 epierotti3 added this to the 1.0 Complete Manuscript milestone May 18, 2023
@wincowgerDEV
Copy link
Collaborator Author

Got some additional feedback from the reviewers on this: openjournals/joss-reviews#5136 (comment)

@shollingsworth I think they are ok with us doing manual tests, but they would prefer we implement some automated user-side tests on the website/container using selenium or something similar if it isn't too crazy to implement.

@Zesky665
Copy link
Collaborator

Zesky665 commented Jun 7, 2023

@wincowgerDEV I read the suggestion in the JOSS thread. I can implement all of those tests using something like Cypress, it shouldn't be much of a hassle.

@wincowgerDEV
Copy link
Collaborator Author

wincowgerDEV commented Jun 7, 2023 via email

@hernandezforges hernandezforges moved this from To-Do to In Progress in TrashAI Jun 8, 2023
@wincowgerDEV
Copy link
Collaborator Author

@Zesky665 should this be closed now thanks to your work in 8c56b8f?

@Zesky665
Copy link
Collaborator

@wincowgerDEV No, me and @shollingsworth still need to add the auto tests to the deployment workflow. We can declare it done after that.

@wincowgerDEV
Copy link
Collaborator Author

wincowgerDEV commented Jun 28, 2023 via email

@wincowgerDEV
Copy link
Collaborator Author

Closing this because we added manual tests now.

@github-project-automation github-project-automation bot moved this from In Progress to Done in TrashAI Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request reviewer comment feedback from manuscript reviewers, should be prioritized
Projects
Status: Done
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants