-
Notifications
You must be signed in to change notification settings - Fork 427
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Demo: Testing frameworks for JavaScript in frontend and backend (#1594)
* added our demo proposal * modified demo proposal
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
24 changes: 24 additions & 0 deletions
24
contributions/demo/week2-testing-and-CI/bonnici-nalenz/README.md
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
Testing frameworks for JavaScript in frontend and backend | ||
|
||
## Names and KTH ID | ||
- Elias Bonnici (bonnici@kth.se) | ||
- Julian Nalenz (nalenz@kth.se) | ||
|
||
## Deadline | ||
|
||
Task 1 | ||
|
||
## Category | ||
|
||
Demo | ||
|
||
## Description | ||
|
||
With the NodeJS ecosystem, JavaScript can be used in both frontend and backend. As with any software stack, unit and integration testing are an essential part, yet selecting the right tool for each individual use case can be a challenge, as NodeJS-based environments can be highly diverse. | ||
|
||
In this demonstration, we show how JavaScript-/NodeJS-based frontends and backends can be tested in real life and how to set up and run such tests with the respective frameworks. Specifically, we will demonstrate the combined use of Jest and Supertest for the backend and its HTTP routes and React Testing Library for the frontend. | ||
|