Sponsored Content
Top Forums Shell Programming and Scripting if, fi, then, and else commands Post 302107415 by sumeet on Friday 16th of February 2007 01:19:04 PM
Old 02-16-2007
hi mheinen

what does this do..check the status of the test..

PHP Code:
if [ $? != ]
then
error message 
fi 
What about multiple test scenarios??

Thanks
Sumeet
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

commands

hi, I'm completely new to FreeBds or unix in general, is there a really nice site to teach you the basic ommands to free BSD. I don't know what to do. =( (3 Replies)
Discussion started by: Special K
3 Replies

2. Shell Programming and Scripting

commands

anyone know the command to display the ten most common words, together with their number of occurences, in the manual entry for the ls command. It would be much useful (1 Reply)
Discussion started by: master_6ez
1 Replies

3. Programming

code that reads commands from the standard i/p and executes the commands

Hello all, i've written a small piece of code that will read commands from standard input and executes the commands. Its working fine and is execting the commands well. Accepting arguments too. e.g #mkdir <name of the directory> The problem is that its not letting me change the directory i.e... (4 Replies)
Discussion started by: Phrozen Smoke
4 Replies

4. Shell Programming and Scripting

Can BASH execute commands on a remote server when the commands are embedded in shell

I want to log into a remote server transfer over a new config and then backup the existing config, replace with the new config. I am not sure if I can do this with BASH scripting. I have set up password less login by adding my public key to authorized_keys file, it works. I am a little... (1 Reply)
Discussion started by: bash_in_my_head
1 Replies

5. AIX

HACMP: difference between 'cl' commands and 'cli' commands

Hi all, I'm new in this forum. I'm looking for the difference between the HACMP commands with the prefix "cl" and "cli". The first type are under /usr/es/sbin/cluster/sbin directory and the second are under /usr/es/sbin/cluster/cspoc directory. I know that the first are called HACMP for AIX... (0 Replies)
Discussion started by: peppix
0 Replies

6. UNIX for Dummies Questions & Answers

help with some commands

Hi! i'd like from someone to explain me 'what is what' from these parts of code if it's possible.i'd like to understand them and their usage: 1) sed '3d' filename 2) sort –t: +0 -1 /etc/passwd and also this: tr ‘’ ‘ ‘ < filename thank you! (11 Replies)
Discussion started by: strawhatluffy
11 Replies

7. UNIX for Dummies Questions & Answers

Need help with certain commands

I'm trying to figure out certain commands for these steps. If you wish to discuss with me in real time, PM me your AIM or MSN, thanks. Here are the steps. Edit the readcal_final file Delete all of the lines that comprise the colandar portion of the memo Without leaving vi, open a new... (0 Replies)
Discussion started by: vgmaster9
0 Replies

8. UNIX for Dummies Questions & Answers

Vi % commands

How can I find a list of shortcut commands I can execute within vi using the % indicator? For example, I can vi a file, press colon, and then type "%s/\r//g" to remove all instances of a carriage return. What else can be executed from the % prompt and what are the shortcut letters (I could type... (4 Replies)
Discussion started by: MaindotC
4 Replies

9. Shell Programming and Scripting

Ls commands

So I need a way to list all files that contain 4 letters. Also separately I need to find a way to list all files with l or n as the third letter of the name. I need to use the ls command and/or grep/egrep. Any help would be a appreciated. (2 Replies)
Discussion started by: muttfacejohnson
2 Replies

10. Homework & Coursework Questions

What are the commands for this ?

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: If the user enters option 1, your program should display the list of entries in the current directory. For... (1 Reply)
Discussion started by: UniverseCloud
1 Replies
SHELLTEST(1)							   version 1.2.1						      SHELLTEST(1)

NAME
shelltestrunner - test command-line programs or arbitrary shell commands SYNOPSIS
shelltest [options] {testfiles|testdirs} DESCRIPTION
shelltestrunner tests command-line programs (or arbitrary shell commands). It reads simple declarative tests specifying a command, some input, and the expected output, and can run them run in parallel, selectively, with a timeout, in color, and/or with differences high- lighted. OPTIONS
-a, --all Show all failure output, even if large -c, --color Show colored output if your terminal supports it -d, --diff Show failures in diff format -p, --precise Show failure output precisely (good for whitespace) -x STR, --exclude=STR Exclude test files whose path contains STR --execdir Run tests from within the test file's directory. Test commands normally run within your current directory; --execdir makes them run within the directory where they are defined, instead. --extension=EXT Filename suffix of test files (default: .test) -w, --with=EXECUTABLE Replace the first word of (unindented) test commands. This option replaces the first word of all test commands with something else, which can be useful for testing alternate versions of a program. Commands which have been indented by one or more spaces will not be affected by this option. --debug Show debug info, for troubleshooting --debug-parse Show test file parsing info and stop --help-format Display test format help -?, --help Display help message -V, --version Print version information -- TFOPTIONS Set extra test-framework options like -j/--threads, -t/--select-tests, -o/--timeout, --hide-successes. Use -- --help for a list. Avoid spaces. DEFINING TESTS
Test files, typically named tests/*.test, contain one or more tests consisting of: o a one-line command o optional standard input (<<<), standard output (>>>) and/or standard error output (>>>2) specifications o an exit status (>>>=) specification Test format: # optional comment the command to test <<< zero or more lines of standard input >>> zero or more lines of expected standard output (or /REGEXP/ added to the previous line) >>>2 zero or more lines of expected standard error output (or /REGEXP/ added to the previous line) >>>= EXITCODE (or /REGEXP/) o A /REGEXP/ pattern may be used instead of explicit data. In this case a match anywhere in the output allows the test to pass. The regu- lar expression syntax is regex-tdfa (http://hackage.haskell.org/package/regex-tdfa)'s. o EXITCODE is a numeric exit status (http://en.wikipedia.org/wiki/Exit_status), eg 0 for a successful exit. o You can put ! before a /REGEXP/ or EXITCODE to negate the match. o Comment lines beginning with # may be used between tests. EXAMPLES
Here's example.test, a file containing two simple tests: # 1. let's test that echo runs. Numbering your tests can be helpful. echo >>>= 0 # 2. and now the cat command. On windows, this one should fail. cat <<< foo >>> foo >>>= 0 Run it with shelltest: $ shelltest example.test :t.test:1: [OK] :t.test:2: [OK] Test Cases Total Passed 2 2 Failed 0 0 Total 2 2 AUTHORS
Simon Michael. shelltestrunner March 18 2012 SHELLTEST(1)
All times are GMT -4. The time now is 05:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy