Colton Sellers
dd4da7ba95
Build & Test Lean / build (push) Has been cancelled
Regression Tests / build (push) Has been cancelled
* Create generic writing for LeanDataWriter, + notes on todos * Make Options Daily/Hourly data store by year * Refactor Generic Write * Permit hour and daily resolutions for options * Refactor writer to merge when needed with other files * Cleanup redundancies, run write tasks in parallel * Make needed classes/vars available * Update tests to reflect new naming convention for daily hourly options data * Add Byte[] overloads for ZipData functions in compression * Implemented Store() for ZipDataCacheProvider * Have LeanDataWriter use a DataCacheProvider * ZipDataCacheProvider cleanup * ZipDataCacheProvider tweaks, doesn't support storing non-zips * Test adjustments * Update LeanDataWriter to use Write instead of SaveDailyHourly/SaveMinuteSecond * Implement tests to verify DownloadAndSave behavior * Nit cleanup on DownloadAndSave tests * Fix for options daily/hourly underlying equity subscription read * Add daily/hourly options data and regressions * Add missing open interest for hourly * Fix writing of OpenInterest Daily/Hourly data * Update data * Fix Date typo in regression * Use daily algorithm to test delisting * Revisions part 1 * Expand test for DataCacheProviders; refactor DiskDataCacheProvider * nit - test adjustments * ZipDataCacheProvider test setup refactor * Adjust multithreaded read/write test; fixes for ZipDataCacheProvider * Move DiskDataCacheProvider to its own file and add write test * Remove _appendToZips; always overwrite entry or create zip * Add mapping regression for daily options * nit - add license to regression * Fix Tick write case where more than one data point for a DateTime * Fix data issue * Address review * Tweaks for tests * Stop Store() early if no entry name is given
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.