This post is related to the private beta test of EDD test automation.
The EDD Test Automation currently does not read your custom Tokenizer command lines (e.g. -k options)
Expected Resolution: Will be fixed in future version
Impact: Test Automation will still run. EDD may not Tokenize.
Workaround: None yet.
Unfriendly errors when missing critical files (e.g. Hart Test System logs; finds more than one .DDL file)
Expected Resolution: Error reporting will be improved on command line execution.
Impact: User may be confused on what is happening
Workaround: The log files have more details on the faulting condition.
For the MFRLOGS, DLL024 requires specific folder.
Expected Resolution: Will be fixed in future version so that logs get uploaded in standard folders
Impact: User needs to create a separate folder for this necessary input
Workaround: Copy DLL024 logs into DLL024 folder.
EDD automation does not cover 100% test points
Expected Resolution: Test points not covered will be marked in the test report. Over time, we will continue to increase scope of automation.
Impact: User may get impression that all test points were performed.
Workaround: Review test specification for complete set of test cases.