On 8/8/06, Jimmy, Jing Lv wrote:
Stepan Mishura wrote:
> On 8/7/06, *Jimmy, Jing Lv* wrote:
>
>
> Sounds pretty good :)
> "exec" do helps, it can check simple situations.
> What I'm concern is that if the return code is not enough for some
> situations, e.g, what exception
Stepan Mishura wrote:
On 8/7/06, *Jimmy, Jing Lv* wrote:
Sounds pretty good :)
"exec" do helps, it can check simple situations.
What I'm concern is that if the return code is not enough for some
situations, e.g, what exception is thrown exactly, or what cause VM exit
ab
On 8/7/06, Jimmy, Jing Lv wrote:
Sounds pretty good :)"exec" do helps, it can check simple situations.What I'm concern is that if the return code is not enough for some
situations, e.g, what exception is thrown exactly, or what cause VM exitabnormally. IMHO, it is still necessary for us.
Hi Jimm
On 8/7/06, Jimmy, Jing Lv <[EMAIL PROTECTED]> wrote:
Leo Li wrote:
> Hi, all:
> I have some idea to test instrument.
> For example, if we would like to test
> Instrumentation.addTransformerwill throw NullPointerException if the
> argument is null,
> we can first write a TestInstrumen
On 8/7/06, Alexey Varlamov <[EMAIL PROTECTED]> wrote:
And you forgot to mention cases when tested VM hangs :)
Still, almost any of those situations may be tested automatically,
just fork a tested JVM and setup timeout watchdog. You may examine
1) return value (via j.lProcess.exitValue());
2) ou
Jimmy, Jing Lv wrote:
> Geir Magnusson Jr wrote:
>>
>> Jimmy, Jing Lv wrote:
>>> Richard Liang wrote:
Jimmy, Jing Lv wrote:
> Hi,
>
> As it is hard to write unit test for package instrument, I now
> have an idea: write down some documents for details of non-unit test
2006/8/7, Jimmy, Jing Lv <[EMAIL PROTECTED]>:
Leo Li wrote:
> Hi, all:
> I have some idea to test instrument.
> For example, if we would like to test
> Instrumentation.addTransformerwill throw NullPointerException if the
> argument is null,
> we can first write a TestInstrument with p
Leo Li wrote:
Hi, all:
I have some idea to test instrument.
For example, if we would like to test
Instrumentation.addTransformerwill throw NullPointerException if the
argument is null,
we can first write a TestInstrument with premain function.
import java.lang.instrument.Instrumentat
Paulex Yang wrote:
Jimmy, Jing Lv wrote:
Hi,
As it is hard to write unit test for package instrument, I now
have an idea: write down some documents for details of non-unit test
cases for instrument. The detail of such test cases contain:
1. The test run on which platform, including speci
Hi, all:
I have some idea to test instrument.
For example, if we would like to test
Instrumentation.addTransformerwill throw NullPointerException if the
argument is null,
we can first write a TestInstrument with premain function.
import java.lang.instrument.Instrumentation;
public cla
Geir Magnusson Jr wrote:
Jimmy, Jing Lv wrote:
Richard Liang wrote:
Jimmy, Jing Lv wrote:
Hi,
As it is hard to write unit test for package instrument, I now
have an idea: write down some documents for details of non-unit test
cases for instrument. The detail of such test cases contain:
Jimmy, Jing Lv wrote:
Hi,
As it is hard to write unit test for package instrument, I now
have an idea: write down some documents for details of non-unit test
cases for instrument. The detail of such test cases contain:
1. The test run on which platform, including special environment;
2. T
Richard Liang wrote:
Jimmy, Jing Lv wrote:
Richard Liang wrote:
Jimmy, Jing Lv wrote:
Hi,
As it is hard to write unit test for package instrument, I now
have an idea: write down some documents for details of non-unit test
cases for instrument. The detail of such test cases contain:
Jimmy, Jing Lv wrote:
> Richard Liang wrote:
>>
>>
>> Jimmy, Jing Lv wrote:
>>> Hi,
>>>
>>> As it is hard to write unit test for package instrument, I now
>>> have an idea: write down some documents for details of non-unit test
>>> cases for instrument. The detail of such test cases contain:
Jimmy, Jing Lv wrote:
Richard Liang wrote:
Jimmy, Jing Lv wrote:
Hi,
As it is hard to write unit test for package instrument, I now
have an idea: write down some documents for details of non-unit test
cases for instrument. The detail of such test cases contain:
Do you mean it's hard
Richard Liang wrote:
Jimmy, Jing Lv wrote:
Hi,
As it is hard to write unit test for package instrument, I now
have an idea: write down some documents for details of non-unit test
cases for instrument. The detail of such test cases contain:
Do you mean it's hard to *write* unit test or i
Jimmy, Jing Lv wrote:
Hi,
As it is hard to write unit test for package instrument, I now
have an idea: write down some documents for details of non-unit test
cases for instrument. The detail of such test cases contain:
Do you mean it's hard to *write* unit test or it's hard to integrate
Hi,
As it is hard to write unit test for package instrument, I now have
an idea: write down some documents for details of non-unit test cases
for instrument. The detail of such test cases contain:
1. The test run on which platform, including special environment;
2. The test description;
3.
18 matches
Mail list logo
