Skip to content

Commit 43b8899

Browse files
authored
Fixed missing package and documented production testing (#124)
Fixed missing package and documented production testing
1 parent 1be0dc8 commit 43b8899

File tree

4 files changed

+316
-8
lines changed

4 files changed

+316
-8
lines changed

CHANGELOG.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
1515

1616
### Fixed
1717

18+
- Fixed the broken production version due to a missing package (#123).
19+
1820
## [1.2.0] - 2024-05-07
1921

2022
### Added

README.md

Lines changed: 29 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ Table of contents:
1515
* [Representation Mapper](#representation-mapper)
1616
* [Using the local pods](#using-the-local-pods)
1717
* [Testing](#testing)
18+
* [Testing the production version](#testing-the-production-version)
19+
* [Testing the development version](#testing-the-development-version)
1820

1921
## Getting Started
2022

@@ -38,7 +40,7 @@ you also need to activate the supporting resources:
3840
1. In a new terminal window, prepare and start the local pods:
3941

4042
```bash
41-
npm run prepare:pods && npm run start:pods
43+
npm run reset:pods && npm run start:pods
4244
```
4345

4446
2. In a new terminal window, start the http proxy:
@@ -217,22 +219,29 @@ You can make use of these for your own tests. Follow these steps:
217219

218220
- Add your data and `.acl` files in the `initial-pod-data` folder.
219221
These files will be available in the pod relative to `http://localhost:8080/example/`.
220-
- Prepare the pods by executing `npm run prepare:pods`.
222+
- Prepare the pods by executing `npm run reset:pods`.
221223

222224
## Testing
223225

224-
For testing we use [Cypress](https://www.cypress.io/). To test, follow the next steps:
226+
For testing we use [Cypress](https://www.cypress.io/).
225227

226-
1. Prepare and start the local pods:
228+
> It is important to test the production version at least at the end of a development cycle.
229+
230+
The development version might be tested repeatedly during development.
231+
232+
### Testing the production version
233+
234+
1. Build the production version of the Web application and serve it:
227235

228236
```bash
229-
npm run prepare:pods && npm run start:pods
237+
npm run build
238+
npx http-server -p 5173 ./dist
230239
```
231240

232-
2. In a new terminal window, start the Web application:
241+
2. In a new terminal window, prepare and start the local pods:
233242

234243
```bash
235-
npm run dev
244+
npm run reset:pods && npm run start:pods
236245
```
237246

238247
3. In a new terminal window, start the http proxy:
@@ -250,5 +259,18 @@ For testing we use [Cypress](https://www.cypress.io/). To test, follow the next
250259
5. Finally, in a new terminal window, you can execute the tests by running:
251260

252261
```bash
262+
## for normal test execution:
253263
npm run test
264+
## for interactive testing:
265+
npm run test:interactive
266+
```
267+
268+
### Testing the development version
269+
270+
The procedure is the same as for testing the production version, except for step 1, which is now:
271+
272+
1. In a new terminal window, start the Web application in development mode:
273+
274+
```bash
275+
npm run dev
254276
```

0 commit comments

Comments
 (0)