disable go test verbose flag #4482
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MaxMustermann2
approved these changes
Aug 3, 2023
Frozen
approved these changes
Aug 3, 2023
ONECasey
approved these changes
Aug 4, 2023
This was referenced Aug 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this pull request, I propose removing the
-vflag from our go test command. Currently, our test suite outputs a substantial amount of data due to our comprehensive test coverage and the number of tests that are run. While the verbosity of our output can be useful in certain situations, it also has the potential to generate a significant amount of noise, which can make it difficult to quickly identify and understand failing test cases.By removing the
-vflag, our test output will become more focused. Instead of printing the results of every individual test, the go test command will only print the results of failing tests. This will make our test logs cleaner and easier to navigate, accelerating the process of locating and debugging failing tests.This change should not impact the effectiveness of our tests or our ability to debug them when they fail. It will simply declutter our test logs and make it easier to spot the important information. I believe this change will benefit our development process and enhance our efficiency.