fixing test problems

This commit is contained in:
adamopolous 2019-08-28 10:46:12 -04:00
parent ace102e180
commit 047404c80d
4 changed files with 6 additions and 2 deletions

View File

@ -184,6 +184,7 @@ public class CodeBrowserOptionsTest extends AbstractGhidraHeadedIntegrationTest
assertEquals("Function Signature Field", groups[idx++]);
assertEquals("Labels Field", groups[idx++]);
assertEquals("Mnemonic Field", groups[idx++]);
assertEquals("Mouse", groups[idx++]);
assertEquals("Operands Field", groups[idx++]);
assertEquals("Pcode Field", groups[idx++]);
assertEquals("Plate Comment", groups[idx++]);

View File

@ -29,8 +29,11 @@ test { t ->
// the class searching environment. This can have a negative impact
// on test results due to the inconsistent Application environment
// which may exist when all tests are run versus a single test.
// Based on this limitation we should only use the Integration base
// test classes within integrationTest regions (e.g., test.slow).
//
// Based on this limitation, do not place tests that depend on integration
// base classes (eg: AbstractGhidraHeadlessIntegrationTest) in 'test'; they
// must go in 'test.slow'.
doFirst {
startTestTimer(t)