[BUILD-1056] Improve magnolia-mgmt unit testing in absence of 3rd party services Created: 17/Apr/23 Updated: 17/Apr/23 |
|
| Status: | Open |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roberto Gomez | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Team: |
| Description |
|
The magnolia-mgmt should be able to run unit tests without any AWS credentials (that is without needing to connect to any AWS account). Now, it's not possible to run magnolia-mgmt test without specifing any AWS credentials ( i.e. AWS_PROFILE_ID env variable), because at least AwsServiceTest.java will check credentials retrieval. There's a point to make a distintion between unit and integration tests, providing mock services for the former, like in JenkinsServiceTest.java. Another alternative to @Mock services for AWS is to try localstack |