Ronit Jain
264c3c8374
* initial commit * Follow IDQH implementation * Expect a list of data handlers from LiveNodePacket * Return null if can not subscribe * refctor to add check for subscription * initialze null * Add tests * Check subscribe retuns null/not-null * cleanup * Read all required IDQH credentails to job * Use CDQH to handle all IDQH instances * constructor abstraction to call from setjob * use flag * remove redundant because derived will call initialize on it * abstract and initialize from setjob * handle null enumerators * get creds from data handlers * handle single data handler value from data-queue-handler * Fix to support a json array * Fix missed constructor call * change access modifier to access from Tests files * Add test to get brokerageFactory from dataQueueHandler * Fix init flag to handle all conditions * Add docs * initialize from setjob * Check if websocket open before using * change defination of initialzie to include tradier * clean up * change defination * fix wrong api key name * return empty enumerator * check websocket open before sending request * check connection before subscribing * fix to include more cases * check websocket open before sending request * Minor refactoring * reafctor and use IsConnected * remove unused * clean up * Fix test cases * reverse change * include config changes * connect to websocket from setjob * check websocket connection from setjob * clean up * include condition for IDQH that are not brokerage * Address review * Add market check condition before subscribe * Remove deprecated * Minor fix for deserializing data queue handler Co-authored-by: Martin-Molinero <martin@quantconnect.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 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.