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

tighten test_umap_sparse_trustworthiness bound #851

Conversation

austereantelope
Copy link
Contributor

Hi,

The test test_umap_sparse_trustworthiness in test_umap_trustworthiness.py has an assertion bound (assert (trust >= 0.85)) that is too loose. This means potential bug in the code could still pass the original test.

To quantify this I conducted some experiments where I generated multiple mutations of the source code under test and ran each mutant and the original code 100 times to build a distribution of their outputs. Each mutant is generated using simple mutation operators (e.g. > can become < ) on source code covered by the test. I used KS-test to find mutants that produced a different distribution from the original and use those mutants as a proxy for bugs that could be introduced. In the graph below I show the distribution of both the original code and also the mutants with a different distribution.

Here we see that the bound of 0.85 is too loose since the original distribution (in orange) is greater than 0.85. Furthermore in this graph we can observe that there are many mutants (proxy for bugs) that are above the bound as well and that is undesirable since the test should aim to catch potential bugs in code. I quantify the "bug detection" of this assertion by varying the bound in a trade-off graph below.

In this graph, I plot the mutant catch rate (ratio of mutant outputs that fail the test) and the original pass rate (ratio of original output that pass the test). The original bound of 0.85 (red dotted line) has a catch rate of 0.63.

To improve this test, I propose to tighten the bound to 0.88 (the blue dotted line). The new bound has a catch rate of 0.69 (+0.06 increase compare to original) while still has >99 % pass rate (test is not flaky, I ran the updated test 500 times and observed >99 % pass rate). I think this is a good balance between improving the bug-detection ability of the test while keep the flakiness of the test low.

Do you guys think this makes sense? Please let me know if this looks good or if you have any other suggestions or questions.

My Environment:

python=3.7.11
numpy=1.20.3

my umap Experiment SHA:
ec9832cbdb7f106a727e6bbd4c54c78fae30f26f

@austereantelope
Copy link
Contributor Author

@lmcinnes Does this look okay to you?

@lmcinnes lmcinnes merged commit e664003 into lmcinnes:master Sep 15, 2022
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.

None yet

2 participants