Staging a component for testing
- Dominant language
- TypeScript
- Stars
- 11.7k
- Forks
- 608
- PR merge metrics
- No merged PRs in 30d
Description
**I'm submitting a bug report**
* **Library Version:**
1.3.1
**Please tell us about your environment:**
* **Operating System:**
Linux (LinuxMint 19.2)
* **Node Version:**
10.16.1
* **NPM Version:**
6.9.0
* **Aurelia CLI OR JSPM OR Webpack AND Version**
JSPM 0.16.55
* **Browser:**
all
* **Language:**
TypeScript 3.6.3
**Current behavior:**
Executing the app and loading views with @useView('resources/panels/data-table-panel.html') works, but running a component test fails. Caused by 404 html-file not found.
By changing the path to @useView('src/resources/panels/data-table-panel.html') the component can be staged, which the leads to a 404 if the app gets started later by serving it with gulp.
Contributor guide
Research direction
Start by reproducing the component test described in the issue, then inspect the referenced Karma configuration and component spec alongside the @useView path. Compare the test setup with the gulp-served application and verify that the component test and running app both resolve the HTML view without a 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100