[CAMEL-20686] camel-core: review File tests for incorrectly shared resources

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.6.0
• Fix Version/s: 4.x
• Component/s: camel-core
• Labels: help-wanted
• Estimated Complexity: Novice
• Assignee: Unassigned
• Reporter: Otavio Rodolfo Piske
• Created: 18/Apr/24 07:42
• Updated: 18/Apr/24 07:42

Description

We have lots of file tests in core that run in parallel and try to write to the same file. This leads to a lot of flakiness in file tests.

 

Look for tests doing things like testFile("output.txt") or testFile("input.txt") or other similar repetitive names (i.e.: foo, bar, etc) should be considered suspicious and need careful review.

 

The tests should be adjusted to one of the following (in order of preference):

• Use separate resources for each test (i.e: "input." + TestClass.class.getSimpleName() + ".txt")
• Use JUnit's 5 temporary file provider
• Use resource locks via JUnit's @ResourceLock annotation.
• Or Isolated if safe to do so