Lines Matching full:patterns

104 #### R5 : The test description shall list the test patterns and input patterns required by the tests
135 #### R12 : The tested function should not know where are the patterns and how to get them 
168 The patterns, output of tests, parameters are also following a hierarchical structure. But they do …
193 A test is requiring input patterns, reference patterns and outputs (to be compared to the reference…
345 According to R12 and R15, tests do not know how to access patterns. It is a responsiblity implement…
347 IO is about loading patterns and dumping output. It is not about IO in general.
352 Patterns is the interface to patterns and output from the test point of view.
364 But it means that no test using patterns shoudl be used in the middle of the test or some part of i…
388 ### Generate the test patterns in Patterns folder
390 We have archived lot of test patterns on github. So this step is needed only if you write new test …
422 You can also use the -e option (for embedded). It will include all the patterns (for the selected t…
529 Client::Semihosting io("../TestDesc.txt","../Patterns","../Output");
535 Client::FPGA io(testDesc,patterns);
538 testDesc and patterns are char* generated by the script processTests and containing the description
563 In DumpOnly mode, reference patterns are not loaded and the test assertions are "failing" but repor…
603              // Definitions of the patterns you have in the test description file
608              // Reference patterns are not loaded when we are in dump mode
625          // Ptr to input patterns, references and output. 
649 Then setUp should load the patterns: