Centralized modification of setenv.* for tomcat when running test on CI

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Testing, Testing > CI environments
• Labels: None

Both selenium test and module integration test need to start tomcat when running test.

We need to a way to modify the java properties using by tomcat so that we can get more info when there is something wrong with tomcat.

Currently we are modifying setenv.* for selenium test and module integration test in different way, selenium test is done in xml, module integration test is done in gradle plugin.

The solution is we move the content we want to change to test.properties, so that each time we only need to modify test.properties and both selenium test and module integration test would be applied.

We have to keep same logic in both xml and gradle plugins, this is because module integration test can be started from gradle alone, if we move all the logic to xml, when you start it from gradle, it won't work.