Changes between Version 8 and Version 9 of Building/RunningTests


Ignore:
Timestamp:
Aug 3, 2007 12:26:59 PM (7 years ago)
Author:
igloo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/RunningTests

    v8 v9  
    195195        '''only_compiler_types(compilers)'''       do this test for certain compilers only 
    196196 
     197        '''expect_broken(bug)''' this test is a expected not to work due to the indicated trac bug number 
     198 
     199        '''expect_broken_for(bug, ways)''' as expect_broken, but only for the indicated ways 
     200 
     201        '''expect_broken_if_platform(bug, plat)''' as expect_broken, but only for the specific platform given 
     202 
     203        '''expect_broken_if_compiler_type(bug, compiler_type)''' as expect_broken, but only for the given compiler type 
     204 
     205        '''set_stdin(file)'''       use a different file for stdin 
     206 
     207        '''exit_code(n)'''          expect an exit code of 'n' from the prog 
     208 
     209        '''extra_run_opts(opts)'''  pass some extra opts to the prog 
     210 
     211        '''no_clean'''              don't clean up after this test 
     212 
     213    These functions should normally not be used; instead, use the `expect_broken*` 
     214    functions above so that the problem doesn't get forgotten about, and when we 
     215    come back to look at the test later we know whether current behaviour is why 
     216    we marked it as expected to fail: 
     217 
    197218        '''expect_fail'''           this test is an expected failure, i.e. there is a known bug in the compiler, but we don't want to fix it. 
    198219 
     
    202223 
    203224        '''expect_fail_if_compiler_type(compiler)'''   expect failure from a certain compiler 
    204  
    205         '''set_stdin(file)'''       use a different file for stdin 
    206  
    207         '''exit_code(n)'''          expect an exit code of 'n' from the prog 
    208  
    209         '''extra_run_opts(opts)'''  pass some extra opts to the prog 
    210  
    211         '''no_clean'''              don't clean up after this test 
    212225 
    213226      You can compose two of these functions together by 
     
    218231}}} 
    219232      as the <opt-fn> argument.  Calls to compose() can of 
    220       course be nested. 
     233      course be nested, but it is simpler to use the composes 
     234      function which takes a list of functions to be composed, e.g.: 
     235{{{ 
     236      composes([omit_ways(['opt']), exit_code(3), expect_broken(123)]) 
     237}}} 
    221238 
    222239    ''<test-fn>''