Skip to content

Latest commit

 

History

History

005-too-many-symbolic-links-encountered

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 

005-too-many-symbolic-links-encountered

spec > minishell > builtins > cd > errors > 005-too-many-symbolic-links-encountered

The purpose of this test is to check that using a symbolic link resulting in ELOOP error as first argument with the builtin cd results in error and not changing current directory.

What is done before test

rm -f "./symbolic_link1" "./symbolic_link2" "./symbolic_link3"
ln -s "./symbolic_link1" "./symbolic_link2"
ln -s "./symbolic_link2" "./symbolic_link3"
ln -s "./symbolic_link3" "./symbolic_link1"

Shell commands that are sent to the standard entry

cd symbolic_link1
${GLOBAL_TMP_DIRECTORY}/display_pwd

What is expected on standard output

expected_to match_regex "PWD:${GLOBAL_TMP_DIRECTORY}:PWD"

What is expected on error output

expected_to_not be_empty
might match_regex "[Tt]oo many.*symbolic links"

Variables

The following variables may appear in this test:

  • ${GLOBAL_INSTALLDIR} -> The installation directory of 42ShellTester
  • ${GLOBAL_TMP_DIRECTORY} -> The temporary directory in which tests are executed
  • ${GLOBAL_TOKEN} -> A token that changes value at launch time
  • ${PATH} -> The standard environment variable PATH
  • ${HOME} -> The standard environment variable HOME

Support binaries

The following binaries may appear in this test:

  • ./display_env -> A binary that iterates on **envp and write each element on standard output.
  • ./display_program_name -> A binary that writes its name on standard ouput.
  • ./display_pwd -> A binary that writes on standard output the absolute path of the current directory returned by getcwd(3), encountered with the strings PWD: and :PWD.
  • ./exit_with_status -> A binary that immediately exits with the status given as first argument.
  • ./read_on_stdin -> A binary that reads on standard entry and write each line on standard output suffixed with the character @ (e.g. same behavior as cat -e and the newline character). When read(2) returns -1, then the string STDIN READ ERROR is written on standard error.
  • ./sleep_and_exit_with_status -> A binary that sleeps for a duration in seconds given as first argument and then exits with status given as second argument.
  • ./sleep_and_write_on_stderr -> A binary that sleeps for a duration in seconds given as first argument and then writes on STDERR the string given as second argument without EOL.
  • ./write_all_arguments_on_stdout -> A binary that writes on standard output each argument separated by the symbol @. If no argument is given, it writes the string "nothing to be written on stdout".
  • ./write_on_stderr -> A binary that writes on standard error the first given argument (the same behavior as echo but with only one argument) and exits with an error status code given as second argument. If no argument is given, it writes the string "write on stderr" and exit with status 1.
  • ./write_on_stdout -> A binary that writes on standard output the first given argument (the same behavior as echo but with only one argument). If no argument is given, it writes the string "write on stdout".
  • ./write_on_stdout_and_stderr -> A binary that writes on standard output the first given argument, and writes on standard error the second given argument. If an argument is missing, it writes the strings "write on stdout" and "write on stderr".