-
Notifications
You must be signed in to change notification settings - Fork 71
Add "test the client" to v5 recipes #329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
144 changes: 144 additions & 0 deletions
144
docs/recipes/developing-and-testing/testing-the-client.md
This file contains hidden or 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,144 @@ | ||
# How do I test the client? | ||
|
||
Testing on the client is a little different than on the server. | ||
|
||
This is because the code which is ultimately being executed in the browser is JavaScript, translated from F# by Fable, and so it must be tested in a JavaScript environment. | ||
|
||
Furthermore, code that is shared between the Client and Server must be tested in both a dotnet environment _and_ a JavaScript environment. | ||
|
||
The SAFE template uses a library called Fable.Mocha which allows us to run the same tests in both environments. It mirrors the Expecto API and works in much the same way. | ||
|
||
## **I'm using the standard template** | ||
**** | ||
If you are using the standard template then there is nothing more you need to do in order to start testing your Client. | ||
|
||
In the tests/Client folder, there is a project named `Client.Tests` with a single script demonstrating how to use Mocha to test the TODO sample. | ||
|
||
>Note the compiler directive here which makes sure that the Shared tests are only included when executing in a JavaScript (Fable) context. They are covered by Expecto under dotnet as you can see in `Server.Tests.fs`. | ||
|
||
#### 1. Launch the test server | ||
|
||
In order to run the tests, instead of starting your application using | ||
```powershell | ||
dotnet run | ||
``` | ||
you should instead use | ||
```powershell | ||
dotnet run Runtests | ||
``` | ||
|
||
#### 2. View the results | ||
|
||
Once the build is complete and the website is running, navigate to `http://localhost:8081/` in a web browser. You should see a test results page that looks like this: | ||
|
||
<img src="../../../img/mocha-results.png"/> | ||
|
||
> This command builds and runs the Server test project too. If you want to run the Client tests alone, you can simply launch the test server using `npm run test:live`, which executes a command stored in `package.json`. | ||
|
||
## **I'm using the minimal template** | ||
|
||
If you are using the minimal template, you will need to first configure a test project as none are included. | ||
|
||
#### 1. Add a test project | ||
Create a `.Net` library called `Client.Tests` in the `tests/Client` subdirectory using the following commands: | ||
|
||
```powershell | ||
dotnet new classlib -lang F# -n Client.Tests -o tests/Client | ||
dotnet sln add tests/Client | ||
``` | ||
|
||
#### 2. Reference the Client project | ||
Reference the Client project from the Client.Tests project: | ||
|
||
```powershell | ||
dotnet add tests/Client reference src/Client | ||
``` | ||
|
||
#### 3. Add the Fable.Mocha package to Test project | ||
Run the following command: | ||
|
||
```powershell | ||
dotnet add tests/Client package Fable.Mocha | ||
``` | ||
|
||
#### 4. Add something to test | ||
|
||
Add this function to Client.fs in the Client project | ||
|
||
```fsharp | ||
let sayHello name = $"Hello {name}" | ||
``` | ||
|
||
#### 5. Add a test | ||
Replace the contents of `tests/Client/Library.fs` with the following code: | ||
|
||
```fsharp | ||
module Tests | ||
|
||
open Fable.Mocha | ||
|
||
let client = testList "Client" [ | ||
testCase "Hello received" <| fun _ -> | ||
let hello = Client.sayHello "SAFE V3" | ||
|
||
Expect.equal hello "Hello SAFE V3" "Unexpected greeting" | ||
] | ||
|
||
let all = | ||
testList "All" | ||
[ | ||
client | ||
] | ||
|
||
[<EntryPoint>] | ||
let main _ = Mocha.runTests all | ||
``` | ||
|
||
#### 6. Add Test web page | ||
|
||
Add a file called `index.html` to the tests/Client folder with following contents: | ||
```html | ||
<!DOCTYPE html> | ||
<html> | ||
<head> | ||
<title>SAFE Client Tests</title> | ||
</head> | ||
<body> | ||
<script type="module" src="/output/Library.js"></script> | ||
</body> | ||
</html> | ||
``` | ||
|
||
#### 7. Add test Vite config | ||
|
||
Add a file called `vite.config.mts` to `tests/Client`: | ||
|
||
``` | ||
import { defineConfig } from "vite"; | ||
|
||
// https://vitejs.dev/config/ | ||
export default defineConfig({ | ||
server: { | ||
port: 8081 | ||
} | ||
}); | ||
|
||
``` | ||
|
||
#### 8. Install the client's dependencies | ||
|
||
```powershell | ||
npm install | ||
``` | ||
|
||
#### 9. Launch the test website | ||
|
||
```powershell | ||
cd tests/Client | ||
dotnet fable watch -o output --run npx vite | ||
``` | ||
|
||
|
||
Once the build is complete and the website is running, navigate to `http://localhost:8081/` in a web browser. You should see a test results page that looks like this: | ||
|
||
<img src="../../../img/mocha-min-results.png"/> |
This file contains hidden or 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
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.
Uh oh!
There was an error while loading. Please reload this page.