running tests

Fredrik Öhrström oehrstroem at gmail.com
Sun Apr 15 22:13:55 PDT 2012


How about this?

make quicktest
# Runs a fast subset that verifies the basic
# functionality of all modules. Should complete
# in less than a minute.

make test
# Runs all tests! Takes a long time.

make performance_tests
# Test performance benchmarks
make gc_tests
# Test garbage collectors
make codegen_tests
# Test the compilers c1/c2/c3.... (oh, do I wish there was only one)

Any more groups of tests Jon?

//Fredrik

2012/4/15 Jonathan Gibbons <jonathan.gibbons at oracle.com>:
> Right now, for a variety of reasons, including performance and reliability,
> there are a number of test targets, each for a different area of tests.
> While a single target for "all" tests might be useful for integrators,
> developers are more likely to ask for and run one of the existing groups of
> tests.
>
> -- Jon
>
>
>
> On 04/15/2012 08:49 AM, Fredrik Öhrström wrote:
>>
>> Sounds reasonable that we should support the same.
>>
>> Perhaps we ought to standardize on a test target so
>> that you do not have to remember the -C.
>>
>> It should be really easy to run all the tests.
>>
>> //Fredrik
>>
>> 2012/4/12 Jonathan Gibbons<jonathan.gibbons at oracle.com>:
>>>
>>> In the old build system, there was a convention along the lines of
>>>
>>>    make&&  make -C test
>>>
>>>
>>> or its equivalent.
>>>
>>>
>>> What are, or will be, the corresponding rules in the new build?
>>>
>>> -- Jon
>
>



More information about the build-infra-dev mailing list