Stefan Zabka
Stefan Zabka
This issue can only be tackled one we have moved the iteration of the CommandSequence and the execution of the individual commands into a single thread. Once this has happened...
Once https://github.com/mozilla/openwpm-crawler/issues/50 has been completed we should update our run book to include this additional check to ensure that we haven't accidentally broken our cloud crawling capability.
This test currently fails.
[JSON Schemas](https://json-schema.org/learn/getting-started-step-by-step.html) allow us to specify every field in our output with a description and a set of constraints that allow verification and deserialization in many different languages including [python](https://json-schema.org/implementations.html#validator-python)....
Currently we know the following: - Running plain FF makes the stackDump API behave as expected. - Running `demo.py` (or tests) and the JS Instrument enabled makes the stackDump API...
In #474 we see in the logs that we can't kill an already killed process. This happens because we [assume that a WebDriverException](https://github.com/mozilla/OpenWPM/blob/16ebe3cc151febc409de5439eb32ec33705c05de/automation/BrowserManager.py#L485) means that we still have a handle...
To understand where we want to go we need to accurately describe the current situation of our tests. What we have: - A lot of integration tests that enable different...
We expect a bunch of exceptions to bubble through the platform, but we don't have tests to ensure this actually works. The ToDo: Throw a bunch of exceptions in a...
Once #750 has landed, the documentation on how to write your custom command should be rewritten.