Feature/establish ci pipeline #23
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Runs only when '[CI]' in commit message - Set up JDK 21 - Build and test with Maven - Exclude testing of application context in CI
- Runs only when '[CI]' in commit message - Mark out "working-directory" of front-end app - Set up Node versions: 16, 18, 21 - Cache package-lock.json file - Clean and install node dependencies - Install React scripts for React app - Build - Test with ESLint
In the CI pipeline, front-end code is tested by a linter, therefore related warnings should have solved, as they can crash a build process.
…ment - Follow end-to-end testing principles - Use H2 in-memory "mock" relational-database - Perform automatic server start during test runs - Perform database initialization before each test
…tests Tests now work with database initialization before each test, therefore getAll API methods should not expect the added record to be present, by previously run add() API method.
Implement a more sophisticated test for Application context load.
As tests now use a "mock" database, there is no further need for database initialization code.
- Add H2 dependency to use during end-to-end testing with refactored test methods. - Resolve a known vulnerability of Spring Web.
- Follow up the changes made for end-to-end testing.
Aim is to express previously implemented end-to-end test upgrade.
…covered [CI] - Refactor useEffect() dependencies. - Refactor setCurrentRecord() state manipulation inside useEffect()s, as "undefined" could have assigned after deletion, which caused the UI to crash.
…ncies [CI]" This reverts commit cac0f76.
|
Should run CI pipeline automatic build and tests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.