... | ... | @@ -17,7 +17,9 @@ Executing Pulse |
|
|
---------------
|
|
|
Being a C++ library, Pulse requires a separate application to instantiate and execute the engine. We will explore various execution mechanisms in our repository in the sections below :
|
|
|
|
|
|
When developing Pulse, we provide a script to run all of our tests, utilities, and tools to help you gather as much information as possible on the impacts of your changes to the overall system. This is the primary tool used when developing Pulse. [More on running the Pulse Test Suite](Test Suite)
|
|
|
When developing Pulse, we provide a script to run all of our tests, utilities, and tools to help you gather as much information as possible on the impacts of your changes to the overall system. This is the primary tool used when developing Pulse. This script can call fuctionality implented in Java or Python. The Pulse repository contains all reqired Java jar files, so we only require that Java is discoverable on your Path. However Python based functionality requires that Python is discoverable on your Path *and* your Python environment has pip installed the packages in our requirements.txt
|
|
|
|
|
|
[More on running the Pulse Test Suite](Test Suite)
|
|
|
|
|
|
We provide a library of scenarios we use to exercise all of the various functionality provided by Pulse. You can directly execute these scenarios and any of your scenairos using our Scenario Driver. This executable will generate a time based CSV file containing the data requested in the scenario. [Learn more about running the Scenario Driver.](Pulse Scenario Driver)<br>
|
|
|
|
... | ... | |