You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ The most important tools that are used in the automated tests are as follows:
11
11
|[xUnit v3](https://xunit.net/?tabs=cs)| The testing framework. You can use any testing framework that you like though |
12
12
|[NSubstitute](https://nsubstitute.github.io/)| Library for mocking. Any mocking library will work. This project doesn't do extensive mocking, but for example `IPublishedValueFallback` is a mandatory parameter for any published content item, even if you don't actually use it. It's just convenient to insert a mock. |
13
13
|[Test Containers](https://testcontainers.com/)| Automatically creates docker containers while running tests. It is used to create an empty SQL Server database that is automatically cleaned up after testing. It is required to have **Docker Desktop** installed and running while running these tests. |
14
+
|[Playwright](https://playwright.dev/dotnet/)| Framework for browser automation. After setting up a content scenario, playwright can open a browser and actually visit the website and make assertions based on content and behaviour in a realistic user interaction. |
14
15
15
16
For a more exhaustive list of tools, I recommend checking out the .csproj files in each testing project.
16
17
@@ -20,6 +21,7 @@ Use this project as a reference to understand how to get started with automated
Alternatively, you can use your automated test explorer in your IDE.
35
+
36
+
| ℹ️ Note on running end-to-end tests |
37
+
|---|
38
+
| Running end-to-end tests is more complicated than running the unit tests and integration tests in this project. The end-to-end tests will likely fail when you run them with the dotnet test command. For detailed instructions, check out the readme in the FunctionTests test project |
0 commit comments