54fce3f666
* change filename template. add fillforward resolution suffix * replicate GH issue 5116 on master it's easy to reproduce on FXCM market by using data resolution different from fillforward resolution. in this cases daily vs hour/minute were added * change priorities of Time & EndTime values. it's necessary to calculate EndTime properly, and then we can align Time to it. potential end time should be also calculated using ptoper TZ. Because of we store open hours without TZ movement TZ in market-hours it's necessary to reapply TZ fix tests * Miss 2AM bar on Sunday of DST; FF 2AM bar on Sunday ST * use UTC TimeZone as baseline during comparison
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 succesful 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.