You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix binary scan tests by creating config once in TestMain setup
The previous fix was creating/deleting config in each test, causing race
conditions when tests ran in parallel or sequentially. Docker tests work
by creating isolated config directories per test via InitTestWithMockCommandOrParams.
This fix creates the CLI config ONCE in setupIntegrationTests() so all
binary scan tests share the same config, preventing conflicts.
Root cause:
- CreateJfrogHomeConfig deletes and recreates the 'default' config
- Calling it in each test caused tests to interfere with each other
- Docker tests avoid this by using isolated config directories per test
Solution:
- Move CreateJfrogHomeConfig call to setupIntegrationTests()
- Only create config when --test.scan flag is set
- Remove individual CreateJfrogHomeConfig calls from all 9 binary scan tests
0 commit comments