Update all tests with suppression codes
See original GitHub issueCan we use the internal flow too to update all suppression codes in one go so that there’s less friction with new flow changes?
sainati Today at 10:38 AM
yes
you can use the tool script that comes with the repo
so ./tool add-comments <SUPPRESSION TEXT> will add suppression comments with the correct codes and that comment
and ./tool remove-comments will remove unused suppressions
this is what we do to upgrade our codebases internally
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Suppress code analysis violations - Visual Studio (Windows)
From the Analyze menu, select Analyze > Build and Suppress Active Issues on the menu bar to suppress all current violations. Suppressing all...
Read more >Suppressing the Reporting of Findings - Parasoft Documentation
This topic explains how to manually suppress Parasoft findings in source code or in a suppression file. See Suppressing Findings in the GUI ......
Read more >Skip tests with global test suppression · Issue #1048 - GitHub
Unit testing : The same test normally is only executed once, to verify the code. The -Skip parameter on It blocks will do...
Read more >Handling Flaky Tests at Scale: Auto Detection & Suppression
Instead of handling test failure detection and suppression at both the PR and the main branch level, it is better to suppress tests...
Read more >List of NFPA Codes and Standards
NFPA 4, Standard for Integrated Fire Protection and Life Safety System Testing ; NFPA 10, Standard for Portable Fire Extinguishers ; NFPA 11,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, I guess some of those buggy warnings were happening in 0.125-0.126 and then fixed in later versions
I’ve run a test on this, you basically need to have both the
flow
andflow-typed
repo’s cloned. Then you’ll need to installflow-bin
in the definitions folder (which can be removed later prior to merging) and have flow on the same version.Then in the flow repo, run,
./tool add-comments ../flow-typed/definitions
where I encountered a few issues,