tree 8f7d4c12c81fbeb69a094eac7228c16327f4c895
parent ee0c789f1b8294e31064b51dafb6560a72e44553
author Marco Miller <marco.miller@ericsson.com> 1585950772 -0400
committer Marco Miller <marco.miller@ericsson.com> 1585950975 -0400

e2e-tests: Unhardcode test scenarios project names

Make the CloneUsingMultiGerrit1 scenario use the automatically generated
project name, which is its own class name. Get its delegate project
scenarios to use that same name consistently. Use an underscore-prefixed
_PROJECT keyword for that purpose, based on the core framework practice.

Have the CreateProjectUsingMultiGerrit and DeleteProjectUsingMultiGerrit
scenarios still support configurable test project names, as independant
scenarios. Reuse core framework's JAVA_OPTS support for that matter, by
means of introducing the PROJECT keyword in scenario json data files.

CloneUsingMultiGerrit1 still enforces its own consistent test project
name, through its aggregating use of CreateProjectUsingMultiGerrit and
DeleteProjectUsingMultiGerrit. The 'project' JAVA_OPTS property
(defining PROJECT) should not be set in that case.

Change-Id: Ib1478381b82cd8cd53cb30522d0f2970edc4bab1