aws-amplify / aws-amplify/amplify-hosting

What does the test>artifacts section of build settings represent for an Angular project?

Open
#2,718 9 comments 0 reactions 0 assignees View on GitHub
documentation hosting question transferred
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

```
test:
phases:
preTest:
commands:
- wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm
- yum install -y ./google-chrome-stable_current_*.rpm
- npm ci
test:
commands:
- npm run test:ci
artifacts:
baseDirectory: ???
files:
- '**/*'
```
`"test:ci": "ng test --no-watch --no-progress --browsers ChromeHeadlessCI",
`

Is it meant to define where all your tests are located? Or is it meant to define where the output artifacts will go after your tests are run? What if my tests don't have an output artifacts (as is the case above), what should I put here?

Contributor guide

Open the contributing guide

Research direction

Start with the test.phases.artifacts section of the build settings and the provided npm run test:ci command, which runs ng test with ChromeHeadlessCI. Confirm whether baseDirectory describes test output or test locations, and document what to configure when the test command produces no artifacts.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular
Domain
ci-cd, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.