Roman Yavnikov
a98a50237b
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
Python Virtual Environments / build (push) Has been cancelled
* feat: helper to return old name of symbols feat: test refactor: test a little bit neat * feat: SplitHistoryRequest() with different mapped symbol feat: test refactor: RetrieveSymbolHistoricalDefinitions * refactor: split historyRequest by historical symbol name refactor: change location of extension refactor: change location of test extension * revert: extra changes * fix: validation on RequiresMapping in SplitHistoryRequest feat: add Future Symbol tests * move: extension method to another file * fix: wrong extension call param position * fix: wrong extension call param position in test * refactor: IEnumerable foreach to more simple form feat: add TickerDateRange struct instead of Tuple fix: test * refactor: map extension alway returns empty result * refactor: SplitHistory extension returns original HistoryRequest * feature: new extension for RequiresMapping except Futures * fix: validation of symbol map file to contains something * refactor: extension test cases * feat: assert of right ticker in tests * fix: split historical request with using Local Time instead of UTC fix: test description * feat: test helper IEnumerable of TimeZones * test: validate right EndDate with different TimeZones * remove: validation of end of date test: several new test cases * feat: additional test with specific dateTime * remove: extra Extension method validation on future and mapping
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.