Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/sqrtneginf/rosettacode-perl-smoke
Smoke testing Perl Rosettacode tasks
https://github.com/sqrtneginf/rosettacode-perl-smoke
perl perl5 rosettacode smoke-testing
Last synced: about 2 months ago
JSON representation
Smoke testing Perl Rosettacode tasks
- Host: GitHub
- URL: https://github.com/sqrtneginf/rosettacode-perl-smoke
- Owner: SqrtNegInf
- Created: 2018-06-30T14:31:18.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2024-04-13T23:17:34.000Z (9 months ago)
- Last Synced: 2024-04-14T01:07:21.731Z (9 months ago)
- Topics: perl, perl5, rosettacode, smoke-testing
- Language: Perl
- Homepage:
- Size: 26 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Smoke testing Perl 5 Rosettacode tasks
Already set up [Perl 6 smoke testing](https://github.com/SqrtNegInf/Rosettacode-Perl6-Smoke), why not Perl 5 too?
How hard can it be? :-)
## 2022 / v5.36
All caught up with backlog (happened some time back in 2020?) and now using v5.36 for testing
(except for a few cases where PDL required, because I cannot get it to work on my creaky old macOS).Mostly keeping up with new tasks as they appear on Rosetta-Code. Sort of. As an experiment, adding
new tasks with v5.36 as a requirement. No one has complained so far. Gotta move forward...## Timeline
Worked through the backlog of existing tasks, and now adding missing ones, where it makes sense.
Initially, testing against the recently-released 5.28 version of Perl.
Once the first pass of all tasks is complete, will then switch to testing against blead.Will be done by Christmas.
## Tools
Re-using my own set of programs ([here](./bin)) from the Perl 6 smoke testing project,
with slight modifications.Relying on [Thundergnat's](http://rosettacode.org/wiki/User:Thundergnat)
very flexible Rosettacode task
[Run examples](http://rosettacode.org/wiki/Rosetta_Code/Run_examples#Perl_6)
to efficiently handle cases where the task has multiple code sections, and to verify that
what I put up on RC actually works correctly.