Hello,
I've created a patch that adds task 'eclipsehwa' (Eclipse 'Hello,
world!' application) to Harmony classlib build.xml . It's attached to
the issue.
You can run
ant -Dharmony.vm.exe=... -Declipse-home=eclipse 3.2 root eclipsehwa
and Eclipse will start, create a project, create a test
Hello,
I've created an Eclipse automated test based on Salikh's code - please see
http://issues.apache.org/jira/browse/HARMONY-752
I've tested it on Windows XP on Eclipse that goes with harmony VM -
eclipse-SDK-3.1.1-win32.zip
Sometimes (irregularry) after execution it prints some stack
Seems, it is not so easy to define the proper test set...
Let's define target to run the integration test. It may be:
1) we want to be sure that all were integrated correctly?
2) or we want to guaranty the 'product quality' for build?
3) some other?
If target is 1) than we should run minimal
Good day,
Anyway it seems that creating an automated Eclipse scenario as
described by Salikh will be useful. I'll try to create the scenario,
corresponding build target and file a JIRA issue with patch for the
new functionality.
On 6/27/06, Vladimir Ivanov [EMAIL PROTECTED] wrote:
Seems, it is
Do not you think these should be different Eclipse scenarios?:
1) simple scenario that run Eclipse, compile small application and runs it
2) simple debug scenario
3) scenario that runs ant-builder
4-N) other scenarios that emulate user work
Am I correct that you are going to use record and play
Vladimir,
Regarding what tool will be used - I don't know yet. I'm studying
Eclipse plugins right now. Seems like the situation with standard
macro recording and playback in Eclipse is not very good now [1], so
the emulation will be based on one of Eclipse plugins or will be a
hand-written
Vladimir Ivanov wrote:
Do not you think these should be different Eclipse scenarios?:
1) simple scenario that run Eclipse, compile small application and runs it
2) simple debug scenario
3) scenario that runs ant-builder
4-N) other scenarios that emulate user work
Doing multiple scenarios
Alexey,
As far as I understand Andrey, he suggests to run tests when a piece
of code is integrated into the code base, by the person who has access
to the repository (committer). A developer shouldn't test his piece of
code on any platform, though it'd be good if he did it and reported
results
Yes, I understand this.
But are you sure that every committer now and in the future has access
to the different platforms and configurations?
Committers, are you? :)
2006/6/26, Anton Luht [EMAIL PROTECTED]:
Alexey,
As far as I understand Andrey, he suggests to run tests when a piece
of code
Alexey Petrenko wrote:
Yes, I understand this.
But are you sure that every committer now and in the future has access
to the different platforms and configurations?
Committers, are you? :)
If I'm patching some general Java code then I just test on my local
workstation and wait for the
Anton Luht wrote:
As far as I understand Andrey, he suggests to run tests when a piece
of code is integrated into the code base, by the person who has access
to the repository (committer). A developer shouldn't test his piece of
code on any platform, though it'd be good if he did it and
Alexey Petrenko wrote:
Some checks before commits are defenetly good...
2006/6/23, Andrey Chernyshev [EMAIL PROTECTED]:
We may probably also need to define the list of
platforms/configurations covered by this procedure.
I'm not sure that I get your idea correctly.
Do you suggest to ask
Folks,
Once we have started to do the changes for drlvm, may be it is a good
time to think about what tests should be passed prior to changes
integration (and what kind of verification to expect before sending a
patch). So far the following comes to my mind:
- running build test (it executes a
Some checks before commits are defenetly good...
2006/6/23, Andrey Chernyshev [EMAIL PROTECTED]:
We may probably also need to define the list of platforms/configurations
covered by this procedure.
I'm not sure that I get your idea correctly.
Do you suggest to ask every developer to make some
14 matches
Mail list logo
