Roman Yavnikov
74d95f1611
* feat: init Download proj * feat: update docker file to copy download proj * feat: parsing in cmd arguments * feat: DataDownloadConfig model feat: add config file refactor: logic of parsing config * feat: overrid ToString in DataDownloaderGetParameters * remove: not used argument command * feat: calculate downloading % (without ETA time) * fix: dockfile copy path for DownloaderDataProvider proj * feat: additional Property in .csproj * remove: DataProviderFullName prop from DataDownloadConfig * remove: extra package (ref from Configuration proj) * feat: ETA calculation of downloading data * Minor tweak * rename: namespace of downloaderDataProvider to generic style format * test: ETA from DownloaderDataProvider * fix: calculate ETA like real downloading process --------- Co-authored-by: Martin Molinero <martin.molinero1@gmail.com>
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.