Anton Luht wrote:
Indeed, unless you are extremely paranoid that all the other API
implementations wrong, but are conspiring to make your test pass then
you should assume that everything else is working ok and you are testing
some specific piece of functionality.
Why should we have gold
Yes, it'll be useful. But currently few resource files follow conventions
only 4 files ...
I created HARMONY-641 with small script to check serialization data file
names.
Results can be placed on wiki or web if needed – is it needed?
Thanks, Vladimir
On 6/20/06, Stepan Mishura [EMAIL
It does not work well. Single resource might be used by many tests
OK.
But in the other case, when one resource is used by one tests (I believe
most typical situation), lets name the resource file using test name.
Thanks, Vladimir
On 6/20/06, Mikhail Loenko [EMAIL PROTECTED] wrote:
Vladimir Ivanov wrote:
On 6/20/06, Gregory Shimansky [EMAIL PROTECTED] wrote:
On Monday 19 June 2006 20:33 Anton Luht wrote:
It is not a good idea to put creation of such resources in something
like setUp() method in JUnit test because who knows if a read-only
file created by VM under
On 6/20/06, Vladimir Ivanov wrote:
Thanks Stepan,
1. The decision about other resource files is: they should be stored into
src/test/resources/ without further naming convention. Right? – then,
a) Ideally, can we specify further (after src/test/resources/)
naming
convention for resource
described on testing and serialization convention pages.
Yes, it'll be useful. But currently few resource files follow conventions
Not only resource files.
The Testing convention document (testing.html) says:
1) Tests, their resources, and support classes are located under
2006/6/20, Vladimir Ivanov [EMAIL PROTECTED]:
Thanks Stepan,
1. The decision about other resource files is: they should be stored into
src/test/resources/ without further naming convention. Right? – then,
a) Ideally, can we specify further (after src/test/resources/) naming
convention for
2006/6/20, Vladimir Ivanov [EMAIL PROTECTED]:
described on testing and serialization convention pages.
Yes, it'll be useful. But currently few resource files follow conventions
Not only resource files.
The Testing convention document (testing.html) says:
1) Tests, their resources, and
Indeed, unless you are extremely paranoid that all the other API
implementations wrong, but are conspiring to make your test pass then
you should assume that everything else is working ok and you are testing
some specific piece of functionality.
Why should we have gold files then? Let's imagine
It would be good if the page
http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.htmldescribes
also location, name convention and
access model for resource files used for testing, specifically, for testing
serialization.
At the present moment test's resource files stored in
Hello Vladimir,
The agreements page on the web site [1] is also of interest here
although it does not dive into any details beyond asking that all
resource files go under module root/src/test/resources.
Seeing as you are canvassing for opinions then my shiny 2 Euro cents
worth is that:
*
On 6/19/06, Vladimir Ivanov wrote:
It would be good if the page
http://incubator.apache.org/harmony/subcomponents/classlibrary/testing.htmldescribes
also location, name convention and
access model for resource files used for testing, specifically, for
testing
serialization.
At the present
Good day,
It seems to me that some tests may require resources that can't be put
to SVN, for example, non-readable files. Non-writable files may fall
in this category, too - I think (sorry it I'm wrong) that after
commit/checkout from SVN they become writable by the owner. Another
example of
On Monday 19 June 2006 20:33 Anton Luht wrote:
It is not a good idea to put creation of such resources in something
like setUp() method in JUnit test because who knows if a read-only
file created by VM under test is really read-only or not :)
Extending this question would be how do you know
Thanks Stepan,
1. The decision about other resource files is: they should be stored into
src/test/resources/ without further naming convention. Right? – then,
a) Ideally, can we specify further (after src/test/resources/) naming
convention for resource files as it is done for serialization
On 6/20/06, Gregory Shimansky [EMAIL PROTECTED] wrote:
On Monday 19 June 2006 20:33 Anton Luht wrote:
It is not a good idea to put creation of such resources in something
like setUp() method in JUnit test because who knows if a read-only
file created by VM under test is really read-only or
16 matches
Mail list logo
