Skip to content

Automate testing of initial sprints in tools module#472

Open
LonMcGregor wants to merge 18 commits intoCodeYourFuture:mainfrom
LonMcGregor:main
Open

Automate testing of initial sprints in tools module#472
LonMcGregor wants to merge 18 commits intoCodeYourFuture:mainfrom
LonMcGregor:main

Conversation

@LonMcGregor
Copy link
Copy Markdown

  • Expected output now in expected folder
  • Github action which runs on push/label
  • Script that can be run to test locally before push

@LonMcGregor LonMcGregor marked this pull request as draft April 7, 2026 15:19
@LonMcGregor LonMcGregor marked this pull request as ready for review April 8, 2026 13:06
Copy link
Copy Markdown
Member

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks really good, and very useful!

One thing I really like about the metadata validator one that this doesn't do is collapse old comments... I just put together CodeYourFuture/trainee-tracker#68 so that we can just run a standalone binary to close existing comments - if we add <!--CYFTT tag: sdc-test-results--> somewhere in the comment we leave, we can use that binary to minimise past comments. WDYT?

- reopened
- synchronize
paths:
- '**.sh'
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this not mean that it won't trigger for the number systems README.md file change?

pull-requests: write

steps:
- name: checkout base branch
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we add a filtering step that cancels this run if there isn't a "Needs Review" label?

And maybe also add a dependency on the 'Validate PR Metadata' workflow so that we don't run if it's failing?

Comment thread test-sdc.sh
pass=$(($pass+1))
else
if [[ "$exercise" == *"stretch"* ]]; then
# echo "Stretch task $directory$exercise failing, you can ignore this if you did not attempt. If you didnt, please have the volunteer check this."
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we check if the file was modified, and ignore if it wasn't?

Comment thread test-sdc.sh
# echo "Stretch task $directory$exercise failing, you can ignore this if you did not attempt. If you didnt, please have the volunteer check this."
total=$(($total-1))
else
echo "Failed $directory$exercise, please either attempt again or have the volunteer check this." >> ../../testoutput.txt
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"have the volunteer check this" - is this an instruction to the trainee ("Please find a volunteer") or to a volunteer ("This PR is in the Needs Review list for a reason") or something else?

Comment thread test-sdc.sh
fi
fi
cat testoutput.txt
elif [[ "$1" == "number-systems" ]]; then
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd be tempted to separate this out into two files? One automatically checked, one manually checked?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants