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: Add Mutation Based Testing #26

Open
dyga01 opened this issue Sep 26, 2024 · 5 comments
Open

Feature: Add Mutation Based Testing #26

dyga01 opened this issue Sep 26, 2024 · 5 comments
Assignees
Labels
future Defer the task for future implementation infrastructure CI/CD configuration test Test cases or test running

Comments

@dyga01
Copy link
Collaborator

dyga01 commented Sep 26, 2024

Description: Both the current and future versions of Execexam should include a better testing structure that includes mutation-based testing. This will allow us to be more confident in our test cases and code.

Expected Behavior: After we are able to integrate the new mutation-based testing, we should be able to see a mutation score for our code. Hopefully, implementing new mutation-based testing will help us discover more bugs in our code.

Actual Behavior: We currently have no mutation-based testing strategy for execexam.

Proposed Solution: Implementing new mutation-based testing using libraries such as mutmut or mutatest. We could do this in our current test files.

@gkapfham
Copy link
Collaborator

Hi @dyga01 what is the priority for this task?

@dyga01
Copy link
Collaborator Author

dyga01 commented Oct 24, 2024

@gkapfham I think that our prioroty should be increasing coverage to be >90% and then we should prioritize this task.

@gkapfham
Copy link
Collaborator

Hi @dyga01 how many weeks off is the resolution of this issue?

@gkapfham gkapfham added future Defer the task for future implementation test Test cases or test running infrastructure CI/CD configuration labels Oct 25, 2024
@dyga01
Copy link
Collaborator Author

dyga01 commented Oct 28, 2024

@gkapfham I am planning on switching to work on a feature in the coming weeks, so I anticipate that I or some other team members could revisit this issue towards the end of the month.

@gkapfham
Copy link
Collaborator

Thanks @dyga01, I encourage you to first work on a feature/bug fix for this tool before you work on another testing task --- I think that it would be rewarding for you to ship this type of work to production. Let me know what you think!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future Defer the task for future implementation infrastructure CI/CD configuration test Test cases or test running
Projects
None yet
Development

No branches or pull requests

2 participants