harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shipilov, Alexander D" <alexander.d.shipi...@intel.com>
Subject RE: [Testing Convention] Stress tests: requirements review needed
Date Thu, 04 May 2006 10:10:03 GMT
Hello, Alexei,

Thank you for reply.

> Do you have in mind some standard glue for these simple building
blocks
> as well? 

Here is a model which describes how to compose simple building blocks.

Let's define the following terms:
   * Brick - any junit Test
   * Generator - junit Test which composes bricks into a stress test

> Do you mean all this rich set of possibilities should be passed via
> command line arguments?

Actually, I meant that test configuration is a String. For example, in
junit this string can be defined in a property file and accessed via
classloader.getResourceAsStream().

> How can we make this notation compact and
> understandable?

Yup. I think we can get a compact notation using Logo-like language.
Here are examples of possible scenario.

1. generator.Thread { Test1 } generator.Thread { Test2 }
This example will launch in parallel Test1 and Test2.

2. generator.Thread { generator.Loop { Test1 } } generator.Thread {
generator.Loop { Test2 } }
Here each of two threads performs a correspondent test in a loop.
            
3. generator.Thread { generator.Package { some.package } }
generator.Thread { generator.Loop { TestGc } }
Here the first thread executes all tests from the given package while
the second thread runs GC.

Thanks,
Alexander Shipilov,
Intel Middleware Products Division

-----Original Message-----
From: Fedotov, Alexei A [mailto:alexei.a.fedotov@intel.com] 
Sent: Tuesday, April 25, 2006 5:10 PM
To: harmony-dev@incubator.apache.org
Subject: RE: [Testing Convention] Stress tests: requirements review
needed

Hi Alexander,

Let me question the following requirement from your list:

>o	System should have a possibility to vary test behavior and
>stress conditions using arguments
>Actually I'm thinking here about a test suite built from a simple
blocks
>like small and fast unit tests, or functional tests

Do you have in mind some standard glue for these simple building blocks
as well? See examples below.

   * Loop generator
     If we have some simple unit or functional test, the reasonable
stress is to execute this test in a loop.

   * Thread generator
     It makes sense to put GC-stressing activity in a loop in parallel
with some test.

   * Stress precondition
     We can fill most of the memory, and run a simple test afterwards.

   * Wildcards in test names
     We may like to stress in some way each test from the package of
tests.

Do you mean all this rich set of possibilities should be passed via
command line arguments? How can we make this notation compact and
understandable?

With best regards,
Alexei Fedotov,
Intel Middleware Products Division

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message