Jhonathan Abreu
d82d70dacf
API Tests / build (push) Has been cancelled
Benchmarks / build (push) Has been cancelled
Build & Test Lean / build (push) Has been cancelled
Regression Tests / build (push) Has been cancelled
Report Generator Tests / build (push) Has been cancelled
Research Regression Tests / build (push) Has been cancelled
Syntax Tests / build (push) Has been cancelled
Python Virtual Environments / build (push) Has been cancelled
* Add 'asynchronous' parameter to trading api * Add regression algorithms * More fixes for asynchronous orders * Fix failing unit tests * Fix failing unit tests * Add multiple orders requests in transaction handler Make each transaction thread handle requests corresponding to the same order * Refactor order state machine in BrokerageTransactionHandler Now using a single dictionary to hold orders and their state, either pending for submission, open or closed. * Revert: remove complete orders from new state machine in BTH * Add order ticket to new BTH open orders state machine * Run syn in Backtesting transaction handler for new orders submission * Remove OpenOrderState.SubmissionPending property * Add Security to OpenOrderState * Minor fix * Cleanup * Some cleanup in BTH * Cleanup * Minor fix * Minor unit test fix * Minor fix * Make Brokerage.ConcurrencyEnable property virtual * Minor change * Cleanup * Add 'asynchronous' parameter to SetHoldings api * Improve regression algorithms
QuantConnect Testing
Before starting any testing, follow the installation instructions to get LEAN running C# algorithms in your machine. For any Python related tests please ensure you have followed the setup as described here.
If the above installation, build, and initial run was successful than we can move forward to testing.
Visual Studio:
Locating Tests
- Open Visual Studios
- Open Test Explorer ("Test" > "Test Explorer")
- The list should populate itself as it reads all the tests it found during the build process. If not, press "Run All Tests" and let VS find all of the tests.
- From here select the tests you would like to run and begin running them.
Failed Test Logs
- On a failed test, check the test for information by clicking on the desired test and selecting "Open Additional Output"
- This will show the stack trace and where the code failed to meet the testing requirements.
Common Problems
Having .NetFramework issues with testing?
- Install NUnit3TestAdapter for VS
Missing dependencies for Python Algorithm?
- Use pip or conda to install the module.