tree 95cfbc0cd6ba5f351b834bdcd7a3dd17ddef0003
parent 37ab73351f84e60d5c7a53221cd9f21abce6da3a
author Marco Miller <marco.miller@ericsson.com> 1585949462 -0400
committer Marco Miller <marco.miller@ericsson.com> 1585951035 -0400

e2e-tests: Unhardcode test scenarios project names

Make the CloneUsingHAGerrit2 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 CreateProjectUsingHAGerrit1 and DeleteProjectUsingHAGerrit
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.

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

Change-Id: I32d74308ae9f52e6ac71d61299db12104f233dff