-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STNG-165 Run one scenario in AWS dev fully end-to-end #182
Conversation
* Refactored quite a bit, to increase on code reuse
…ly the same code and parameters does work
@@ -16,9 +16,6 @@ jobs: | |||
steps: | |||
- name: Checkout repository | |||
uses: actions/checkout@v4 | |||
with: | |||
ref: ${{ env.AWS_ENVIRONMENT }} | |||
# Enforces only AWS env name matching branches are checkout and deployed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was a pain.. I was making experimental changes in the pom.xml
file for the new situation, but they were not applied, because I changed the checkout here to force it to dev
HEAD instead.
The enforcing of the right environment is also already guaranteed by line 5 and line 10 of this file.
<junit.excludedTags>WebUI</junit.excludedTags> | ||
</properties> | ||
</profile> | ||
</profiles> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I introduced profiles to make it more clear and easy to use and select which profile you'd like to use. By default, the first profile is used.
Created test
AWSEnvironmentTest
which runs Ebl, Conformance TD-only, Carrier fully end-to-end.Created the SeleniumTestBase for code reuse. It does not start Spring Boot itself.
Sorry for the refactoring and changes in the same PR.. which makes it harder to see the changes.