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.

Sign up for GitHub

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

Jump to bottom

[DOC] Improve E2E testing for tools #970

Closed
parthosa opened this issue Apr 26, 2024 · 0 comments · Fixed by #1313
Closed

[DOC] Improve E2E testing for tools #970

parthosa opened this issue Apr 26, 2024 · 0 comments · Fixed by #1313
Assignees
@parthosa
Labels
core_tools Scope the core module (scala) documentation Improvements or additions to documentation

Comments

@parthosa
Copy link
Collaborator

parthosa commented Apr 26, 2024 •
edited
Loading

As the tools development proceeds with newer features, more arguments and customer engagement, we should improve the testing capabilities of tools to be more resilient to errors or unexpected results. We should develop a comprehensive testing scheme tools.

Routemap

  1. Existing:
    1. Evaluate Tests Coverage
    2. Assess Test Effectiveness
  2. Next Steps:
    1. Identify Scenarios with Gaps - Common and frequent error cases, prioritization
    2. Design and add missing tests
    3. Maybe create test documentation
    4. Automation and monitoring

cc: @mattahrens
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@parthosa parthosa

Labels
core_tools Scope the core module (scala) documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add end-to-end behavioural tests for the python CLI parthosa/spark-rapids-tools
3 participants
@mattahrens @parthosa @amahussein