-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Refactor logging condition and update testsets
- Loading branch information
Showing
18 changed files
with
2,158 additions
and
156 deletions.
There are no files selected for viewing
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,29 @@ | ||
# 🧪 Emergency Stop & Recover Testset | ||
|
||
This directory contains all the runs for the Emergency Stop & Recover testset. | ||
|
||
This process uses instances of the previously defined `Start Wait Stop` testset! | ||
|
||
## 💡 Explanation | ||
|
||
![Process Diagram](https://raw.githubusercontent.com/ylkhayat/smart-socket-service/main/docs/testsets/emergency-stop-recover/emergency-stop-recover.svg) | ||
|
||
### Literal Description | ||
|
||
The testset simulates a loop that is of 7 iterations. Each iteration starts with a script that generates 3 data element numbers, the first is the duration of the `toggleDuration` (the time we have to wait between starting and closing) for the first subprocess. The second is the duration of the `toggleDuration` for the second subprocess. The third is the duration of the timeout that is placed behind the second subprocess. This was done to achieve some kind of randomness in the testset, where subprocesses are harmonically communicating with the smart socket. | ||
|
||
### Real-life Scenario | ||
|
||
Unlike the `smart-wait-stop`, this one assumes many people want to control the exact same smart socket concurrently. A real-life scenario could be a shared office space where different teams want to use the same projector. Each team wants to turn on the projector, use it for a certain duration, and then turn it off. However, if one team's usage overlaps with another, the projector should stay on. Thus, we want to start the projector, wait for it to be used for a certain duration, and then stop it. If the projector is already on, we don't need to do anything - as long as it stays on for the duration needed. | ||
|
||
Once again, refer back to my personal explanation of what is a testset (the `start-wait-stop` one) in the document [start-wait-stop](https://ylkhayat.github.io/smart-socket-service/testsets/#start-wait-stop.pdf) 🚀 | ||
|
||
## 📊 HTML Reports | ||
|
||
Please click on each [`run-<x>/README.md`] to view what is happening in each run and further information on why is a run different from another. | ||
|
||
- [Run 1](https://ylkhayat.github.io/smart-socket-service/testsets/#emergency-stop-recover/run-1/README.md) | ||
|
||
## Run the thing online! | ||
|
||
You can start a process through this link which will take you to cpee.org and start the process for you! [Click me to create a process and get started!](https://cpee.org/flow/graph.html?load=https://raw.githubusercontent.com/ylkhayat/smart-socket-service/main/docs/testsets/emergency-stop-recover/emergency-stop-recover.xml) |
Oops, something went wrong.