On Sun, Oct 5, 2014 at 1:51 PM, Erich Steinböck <erich.steinbo...@gmail.com>
wrote:
> Oops, make that the "::resource" directive...
>
>
> I'd volunteer, too. Maybe something simple for a start: .RexxInfo?
>
RexxInfo would be a good start. Do you need the list of methods
implemented?
>
> Might I possibly get any needed permissions to do svn commits for ooTest
> cases by myself without having to go through the (somewhat cumbersone)
> process of submitting patches?
>
Sorry, but we keep tight control over svn access to committers because it
is not possible to give permission to just a portion of the source tree.
Patches will have to suffice. I suggest using the
Test Case tracker system for this exercise.
https://sourceforge.net/p/oorexx/test-cases/
>
>
> Erich
>
>
> On Sun, Oct 5, 2014 at 6:44 PM, Rick McGuire <object.r...@gmail.com>
> wrote:
>
>> Oops, make that the "::resource" directive...
>>
>> Rick
>>
>> On Sun, Oct 5, 2014 at 12:40 PM, Sahananda (Jon) Wolfers <
>> sahana...@windhorse.biz> wrote:
>>
>>> Thanks Rick,
>>>
>>> Asset directive is mine. I'll see what I can do.
>>>
>>> Jon
>>>
>>> On 5 October 2014 17:07, Rick McGuire <object.r...@gmail.com> wrote:
>>>
>>>>
>>>> On Sun, Oct 5, 2014 at 11:54 AM, Sahananda (Jon) Wolfers <
>>>> sahana...@windhorse.biz> wrote:
>>>>
>>>>> A tutorial on using the test framework is available here
>>>>> <http://sourceforge.net/projects/oorexx/files/oorexxunit/4.2.0.Snapshot.06/>
>>>>> (called
>>>>> quickstart.pdf)
>>>>>
>>>>> Mark announced this on the RexxLa list back in February in the context
>>>>> of this appeal
>>>>>
>>>>>> A quick announcement that an ooTest-4.2.0-snapshot06 package is now
>>>>>> available for download from SourcForge:
>>>>>>
>>>>>> https://sourceforge.net/projects/oorexx/files/oorexxunit/4.2.0.Snapshot.06/
>>>>>> This snapshot represents the current state of the test suite used to
>>>>>> test ooRexx 4.2.0.
>>>>>> There has been a lot of information written on how to use the test suite
>>>>>> and that information is available in the ooTest-4.2.0-snapshot06 package.
>>>>>> If, after reading that information, there are any questions regarding the
>>>>>> test suite, please post a question on any of the lists where
>>>>>> discussions concerning ooRexx take place.
>>>>>> It has always been the hope of the ooRexx development team that users
>>>>>> would help test ooRexx by running the test suite and participate in
>>>>>> improving the test suite by writing test cases.
>>>>>> Any and all questions regarding the test suite, or requests for help
>>>>>> in writing test case, are welcome and will be addressed by one of
>>>>>> the developers.
>>>>>> Thank you,
>>>>>> The ooRexx Project Team
>>>>>
>>>>>
>>>>> As I understand it a future new version 5.0.0 is available from the
>>>>> build machine.
>>>>>
>>>>> You can find it here <http://build.oorexx.org/downloads/>.
>>>>>
>>>>> For windows platforms you download an installer, just like you did
>>>>> when you last upgraded and you can just install it on your machine. When
>>>>> you have finished testing, you can just get the installer for your current
>>>>> version from sourceforge
>>>>> <http://sourceforge.net/projects/oorexx/files/> (or your download
>>>>> folder) and install it back. The only exception I am aware of is if you
>>>>> have installed an independent version of ooDialog, in which case you will
>>>>> need to reinstall that after you have installed your previous version of
>>>>> ooRexx. For other platforms, you will no doubt know what to do.
>>>>>
>>>>> I assume there is some value in your just downloading the new version
>>>>> and checking that what you run on the old version still runs on the new
>>>>> version and raising bug reports
>>>>> <http://sourceforge.net/p/oorexx/bugs/> where it doesn't.
>>>>>
>>>>> There is more value still in you running the test suite.
>>>>>
>>>>> What Rick is asking for is for you to read Mark's paper and offer to
>>>>> write new test cases for the heaps of new and exciting functionality that
>>>>> is in 5.0.0.
>>>>>
>>>>> Rick, I anticipate having a bit of free time over the next few weeks,
>>>>> could you suggest something that I might write a test case for?
>>>>>
>>>>
>>>> Well, since you were the one who asked for it, how about some tests for
>>>> the ::asset directive? You might want to look at what I did some of the
>>>> other directive tests for testing package dynamically. You might note I
>>>> also made good use of the new array shortcut in writing those tests :-)
>>>>
>>>> Rick
>>>>
>>>>
>>>>>
>>>>> thanks,
>>>>>
>>>>> Jon
>>>>>
>>>>>
>>>>> On 4 October 2014 23:05, Chip Davis <c...@aviatrexx.com> wrote:
>>>>>
>>>>>> Well Rick, I find flying a helicopter "not that hard to learn" too but
>>>>>> most folks beg to differ. ;-)
>>>>>>
>>>>>> You need to gently coach Les or Walter through the process and have
>>>>>> them tell the rest of us mere mortals that it's easier than it looks.
>>>>>>
>>>>>> Is there a tutorial or readily available documentation on the care and
>>>>>> feeding of the test framework? Sometimes, getting over the first
>>>>>> learning curb is the biggest hurdle.
>>>>>>
>>>>>> -Chip-
>>>>>>
>>>>>> On 10/4/2014 5:35 PM, Rick McGuire wrote:
>>>>>> > We have the build machine issues more or less worked out so that
>>>>>> we're
>>>>>> > getting daily builds on the trunk version again. Anybody interested
>>>>>> > in writing test cases for any of the new features? ...cue the sound
>>>>>> > of crickets chirping :-)
>>>>>> >
>>>>>> > You will need to learn how to write tests using the test framework,
>>>>>> > which seriously, is not that hard to learn and there are lots of
>>>>>> > examples in our test suite to work from.
>>>>>>
>>>>>>
>>>>>>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
