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

Add analysis-time tests for the fuzzing_dictionary() rule #42

Open
stefanbucur opened this issue Jul 17, 2020 · 2 comments
Open

Add analysis-time tests for the fuzzing_dictionary() rule #42

stefanbucur opened this issue Jul 17, 2020 · 2 comments
Labels
code health Cleanup or testing task that improves the codebase good first issue Good for newcomers priority:medium
Milestone
Iteration 9

Comments

@stefanbucur
Copy link
Collaborator

No description provided.

@stefanbucur stefanbucur added the code health Cleanup or testing task that improves the codebase label Jul 17, 2020
@stefanbucur stefanbucur added this to the Iteration 9 milestone Jul 17, 2020
@tengpengli
Copy link
Contributor

I am not sure I understand this issue correctly. Do you mean we need a test to calculate the average time cost of running fuzzing_dictionary() by testing it for multiple (say, 50) times?

@stefanbucur
Copy link
Collaborator Author

Ahh, sorry for the confusing title. I was having in mind Starlark's own unit testing framework, documented at https://docs.bazel.build/versions/3.4.0/skylark/testing.html. They are referring to this framework as checking "analysis-time behavior" of rules.

@stefanbucur stefanbucur added the good first issue Good for newcomers label Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code health Cleanup or testing task that improves the codebase good first issue Good for newcomers priority:medium
Projects
None yet
Milestone
Iteration 9
Development

No branches or pull requests
2 participants
@stefanbucur @tengpengli