Updated readme to reflect testing implementation.
This commit is contained in:
parent
c7dae0bdb3
commit
08150e8d96
12
README.md
12
README.md
@ -16,6 +16,18 @@ This will handle starting a new container of Next.js with all required packages
|
|||||||
|
|
||||||
Keep in mind that you should **never** host this site in development mode publicly. This sentiment reflected in the documentation for Next.js.
|
Keep in mind that you should **never** host this site in development mode publicly. This sentiment reflected in the documentation for Next.js.
|
||||||
|
|
||||||
|
## Testing
|
||||||
|
|
||||||
|
It's in the preliminary stages right now, but if you want to try your hand at running automated browser tests yourself:
|
||||||
|
|
||||||
|
```
|
||||||
|
./run_tests.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
That will start up a docker compose setup with a Selenium standalone server and a Python runner for the test script(s). I plan to add much more here in the future, like the ability to specify which test suites to run, what URL to test at, organizing output, etc.
|
||||||
|
|
||||||
|
For now, this will just run a test that opens the browser to [werefox.cafe](https://werefox.cafe) and waits 10 seconds, then closes. Just a small smoke test.
|
||||||
|
|
||||||
## Production
|
## Production
|
||||||
|
|
||||||
You can also use the `deploy.sh` script to start up the container in production mode.
|
You can also use the `deploy.sh` script to start up the container in production mode.
|
||||||
|
Loading…
Reference in New Issue
Block a user