-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task list #3
Comments
Currently re-evaluating choice of unit test framework. |
Yes, that's a tricky question. In the COBOL track we went through I think
two other possibilities before we settled on the current. As for the 8th
track, I had to write my own.
…On Sun, 29 Jan 2023 at 06:26, Anthony J. Borla ***@***.***> wrote:
Currently re-evaluating choice of unit test framework.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABTFVLYM63JYBWLL4XM47LWUWMKHANCNFSM6AAAAAASPJQ5KQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The BATS approach initially looked suitable, but it requires the Rexx scripts to emit output. Simple, doable, but clunky. I would like something a little more elegant. So, I can go the custom route, but I think extending t-rexx (to return success / failure code, emit TAP output, and trap STDOUT-bound output from Rexx SAY) more meets the elegance criterion, plus gives that project more exposure as the official unit test framework for Exercism Rexx. Will be proceeding with this after I have implemented a few more Practice Exercise skeletons. |
I have marked off exercises I will be implementing over the next few weeks. |
Replacement test unit framework appears to be meeting expectations. Two practice exercises down, approximately twenty-odd to go ... |
This comment was marked as off-topic.
This comment was marked as off-topic.
Continuing to implement exercises, and will do so until 20+ exercise target met. Will then start unit test framework overhaul. |
Since I am ahead of my self-imposed schedule, and am enjoying implementing these exercises so much, I am aiming to implement 40+ exercises before proceeding to a subsequent stage (either unit test framework expansion, or CI tasks). |
Just hit 51 exercise implementations. Will cease at 71, then move onto subsequent stages. |
Wow. I stopped at 20 for civil and 8th as that was the bare minimum and I
was impatient.
…On Fri, 17 Mar 2023, 11:29 am Anthony J. Borla, ***@***.***> wrote:
Just hit 51 exercise implementations. Will cease at 71, then move onto
subsequent stages.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABTFVIO7DR2RSA6QFC2VGTW4PLARANCNFSM6AAAAAASPJQ5KQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This will, most likely, be my only Exercism track, so I want to make it as solid, and substantial, a piece of work as I can. |
Fair call. You can add tasks post-launch.
…On Sat, 18 Mar 2023, 7:45 am Anthony J. Borla, ***@***.***> wrote:
This will, most likely, be my only Exercism track, so I want to make it as
solid, and substantial, a piece of work as I can.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABTFVMGIUYI4Y2HH5434XDW4TZQHANCNFSM6AAAAAASPJQ5KQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The text was updated successfully, but these errors were encountered: