8149c291fc
API Tests / build (push) Has been cancelled
Benchmarks / build (push) Has been cancelled
Regression Tests / build (push) Has been cancelled
Build & Test Lean / build (push) Has been cancelled
Python Virtual Environments / build (push) Has been cancelled
Report Generator Tests / build (push) Has been cancelled
Research Regression Tests / build (push) Has been cancelled
* Add unit test reproducing the bug * Improve unit test * Apply market hours database updates to instance Make sure entries are updated instead of overridden so that consumers holding the mhdb can pick up the changes * Improved unit tests * Update data folder MHDB entries instead of overriding instance * Optionally reset custom mhdb entries on reset * Simplify mhdb reset in live trading Cleanup and minor fixes * Ensure symbol properties database updates are picked up by consumers Update SPDB entries instead of overriding them, just like for the MHDB so that consumers pick up updates after refresh * Fix for symbol properties update thread safety * Minor improvements and cleanup * Mhdb and spdb update logic simplification * Move "force exchange always open" logic to mhdb * Simplify symbol properties holder and updates * Refactor security databases to use a common base class Introduce BaseSecurityDatabase<T, TEntry> to encapsulate common functionality for MarketHoursDatabase and SymbolPropertiesDatabase. * Cleanup
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.