Weimin Yu 3c18f64710 Fix flaky tests due to Entity name conflicts (#569) ... * Fix flaky tests due to Entity name conflicts Objectify siliently replaces current registration of a given kind when another class is registered for this kind. There are several TestObject classes in the current code base, which by default are all mapped to the same kind. Tests have only been flaky because impacted tests need to run in specific orders for failures to happen. Using multiple executors in Gradle also reduced the likely hood of errors. To reproduce the problem run the following tests in order (e.g., by putting them in a test suite): 1. ExportCommitLogDiffActionTest 2. CreateAutoTimestampTest 3. RestoreCommitLogsActionTest In this PR, we - Made sure all entities have unique kinds. - Made all test entities register with AppEngineRule instead of directly with ObjectifyService. - Added code in AppEngineRule to check for re-registrations. - Added presumit check for forbidden direct registration.		2020-04-28 15:32:42 -04:00
..
checkstyle	Upgradle JUnit to 4.13 (#442)	2020-01-14 10:54:09 -05:00
dependency-license	Start using JUnit 5 (#488)	2020-02-19 18:29:59 -05:00
nom_build.py	Create a nom_build wrapper script (#508)	2020-03-10 16:32:14 -04:00
nom_build_test.py	Create a nom_build wrapper script (#508)	2020-03-10 16:32:14 -04:00
presubmits.py	Fix flaky tests due to Entity name conflicts (#569)	2020-04-28 15:32:42 -04:00