vfurmane / pipex-tester

Project Tester - Pipex

Pipex Tester

This repo provides test scripts for your pipex project @42School.

Note that the tester doesn't check the norm. The purpose of this repo is to be more effective in evaluation, not to botch it up.

Furthermore, the tester is absolutely not official and many tests may be irrelevant. It is intended for helping you design your project. Please do not use it as an absolute reference during defense.

Installation

First things first, clone this repo (the preferred path is alongside the pipex's directory).

git clone https://github.com/vfurmane/pipex-tester

Usage

./run.sh [-cltu] [tests_no]...

Once the installation is done, cd into the tester's directory, and run the ./run.sh script. You should be prompted some configuration questions. If you have answered any of them incorrectly, you can execute ./run.sh -c or ./run.sh --config to be prompted the questions again.

To stop the tester earlier, you can press Ctrl-C, and it will show you your grade at that moment.

The logs are stored in the outs directory. You'll find three types of file:

• test-xx.txt: this is the outfile of pipex.
• test-xx-original.txt: this is the outfile we would get with bash.
• test-xx-tty.txt: this is what your program writes (stdout and stderr)
• test-xx-exit.txt: this is the exit code of your program

You may find files like that test-xx.x.txt. These are log files for command executed twice during the same test.

There is a man page for the tester:

man ./man/man1/pipex-tester.1

Arguments

test number

Run the specified tests.

./run.sh 1 2 3

-c

Allow you to reconfigure the tester.

./run.sh -c

-l

Disable the leaks tests.

./run.sh -l

-t

Disable the timeout tests. May run the tests faster.

./run.sh -t

-u

Force the tester to update (if needed only).

./run.sh -u

Troubleshooting

If you encounter another problem, please feel free to open an Issue using the GitHub's tab.

pipex-tester's Issues

Add test for cases where $PATH is empty/unset

Hello, your tester is very clean, I like it a lot. I would like to suggest you to add a test where $PATH is empty/unset.

Need help with the test 14.

Hi im trying to check the 14th test: The program uses the environment list. Can you help me with that? Thanks.

run.sh -c doesn't work but change pipex-tester/script/config.sh then work fine

pipex-tester/scripts/config.sh

Line 22 in 38cc969

read -N 1 -r check_update

I'm using MacOs BigSur & Mac Air 2020.
when run.sh -cdoesn't work for my cadets.
like as.

So, just Changeread -N 1 -r check_update TO read -n 1 -r check_update then work fine

Tests number should be expected any number of times in the README

In the README, the syntax for the [tests_no] should be [tests_no]... as any number of tests is expected in the script’s parameters.

The man should probably be updated too.

Test Result

Describe the bug :

When executing the script, i have one KO which is : The program uses the environment list
i don't get what is the error behind this?
can u explain?

Thank you

Test 1 & 2 failed

Describe the bug
In my case, I see 'KO' for tests #1 & #2, when in my terminal I don't have any problem compiling.

Expected behavior
Tests 1 & 2 being OK

Desktop (please complete the following information):

• OS: Windows 11 + WSL2

edit : replaced text with latest picture.