Sponsored Content
Full Discussion: Test: argument expected
Top Forums Shell Programming and Scripting Test: argument expected Post 302844537 by bakunin on Monday 19th of August 2013 10:59:17 AM
Old 08-19-2013
Quote:
Originally Posted by smkremer
Code:
cd $1

if [ $2 = "test.txt" ]; then

The prolem is probably one of the lines i have quoted or the similar lines in your code. You should always quote such strings, in case they are empty or containing blanks, tabs and other special characters:

Code:
cd "$1"

if [ "$2" = "test.txt" ]; then

etc..

I hope this helps.


bakunin
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

ERROR-> test: argument expected , what does it mean?

I am trying to compare two integer variables in the if statement, but i am getting this "test:argument expected". What am i missing? Why is the if loop not executing correctly? trunkPCM="100000"; more $FILE |while read line do PCM=`echo $line | awk '{ print $2 }'` ... (4 Replies)
Discussion started by: tan102938
4 Replies

2. UNIX for Dummies Questions & Answers

test:argument expected

Hi all, I am getting "test:argument expected" error in the following script LOGDIR=$XXAR_TOP/log PROGRAM_NAME=XXAR_GPS_LBFDMSGEN .. .. .. Check_Errors() { sqllogfile=$1 cd ${LOGDIR} countfile=${LOGDIR}/${PROGRAM_NAME}.tmp echo "countfile is " $countfile >> $LOGFILE echo... (4 Replies)
Discussion started by: rrs
4 Replies

3. Shell Programming and Scripting

test: argument expected

Can someone help me with a very simple query I have the following script: #!/bin/sh VAR1="" if then VAR1="Message" fi echo $VAR1 put when i run it i get the following error test_job.sh: test: argument expected (5 Replies)
Discussion started by: andy202
5 Replies

4. Shell Programming and Scripting

test: argument expected

I'm newbie to coding script so i found test: argument expected when i run it. please help me a=`df -k |awk '{print $5 }'|egrep "(100%|%)"|cut -d"%" -f1|tail -1` if then df -k|egrep "(100%|%)"|awk '{print $1,$5,$6}' else echo "No disk capacity more than 80%" fi thk in advance (7 Replies)
Discussion started by: unitipon
7 Replies

5. Shell Programming and Scripting

test: argument expected

+ test.sh: test: argument expected #!/bin/bash if then echo thennnn else echo elseeee fi why does it show this error? Clearly from debug mode, the argument is passed. I also tried if Run on Solaris 9. Thanks (10 Replies)
Discussion started by: lalelle
10 Replies

6. Shell Programming and Scripting

Test: argument expected.

Hi, Since i am new to Unix and on suggestion on some smart guys on unix... i have decide to learn more deeply on Unix...so i was kind of playing with if statements and found this error... though i tried to correct is for hours now i couldnt find whats wrong in my loop. if then ... (4 Replies)
Discussion started by: bhagya2340
4 Replies

7. Shell Programming and Scripting

test: argument expected

# to search a file if it exists and whether its readable or not # if yes print its first 5 lines echo enter the filename to be searched read fname if #-d $fname then echo file doesn exists elif then echo its a directory elif then cat $fname else echo its not readable fi # end of... (9 Replies)
Discussion started by: gotam
9 Replies

8. Shell Programming and Scripting

error : test: argument expected

Hello all, I am trying to figure out why i am getting an error while executing the script...altought it seems like its work...but still get the test arguement error...any help would be appericiate...this script basically connects to any oracle db ( just have to pass db name to it)... (4 Replies)
Discussion started by: abdul.irfan2
4 Replies

9. UNIX for Advanced & Expert Users

Error:--test: argument expected--Even though i give an argument.

Hi All, I am running the script VBoxManage list vms |sed 's/"//g' | cut -d " " -f1 > har1out.mytxt result=`cat har1out.mytxt | grep $1' echo $result echo $1 { if then echo pass else echo fail fi (2 Replies)
Discussion started by: harsha85
2 Replies

10. Shell Programming and Scripting

Error- test: argument expected

check_build_info_table() { if then export build_info_table=`sqlplus -s sna/dbmanager <<! set pagesize 0 heading off feedback off SELECT DISTINCT TABLE_NAME FROM ALL_TABLES WHERE OWNER = 'XYZ' AND TABLE_NAME = 'MY_TABLE'; exit !` ... (3 Replies)
Discussion started by: ambarginni
3 Replies
Test::Assertions::TestScript(3pm)			User Contributed Perl Documentation			 Test::Assertions::TestScript(3pm)

NAME
Test::Assertions::TestScript - Base for test scripts SYNOPSIS
use Test::Assertions::TestScript; use Module::To::Test qw( frobnicate ); ASSERT(frobnicate(),"Frobnicate returns true"); DESCRIPTION
Test::Assertions::TestScript provides a base for writing test scripts. It performs some common actions such as setting up the @INC path and parsing command-line options, specifically: o The lib and t/lib directories are added to @INC. o The current directory is changed to the directory the script is in. o Test script command-line options are parsed. (See "COMMAND-LINE OPTIONS") o The test set of functions from Test::Assertions are imported into your test script. Test::Assertions::TestScript makes certain assumptions about the filesystem layout of your project: o Modules that you are testing are in the lib directory of your project. o Test scripts are in the t directory. o There may also be a t/lib directory for any modules written for the test process. Test::Assertions::TestScript should be "use"d before any modules that you intend to test. OPTIONS
Options can be supplied to the import function. These should be placed after the "use" or "import". For example use Test::Assertions::TestScript( tests => 10, options => { 'b', $opt_b }) The following options are defined: tests The number of tests to pass to "plan tests" from Test::Assertions. For example to tell Test::Assertions::TestScript that the script contains 42 tests: use Test::Assertions::TestScript tests => 42; options A hashref of additional options to capture via Getopt::Long. The "options" import parameter is passed verbatim to GetOptions, so something along the following lines is required in order to capture the "-b" command line option: use Test::Assertions::TestScript( options => { 'b' => $opt_b } ); COMMAND-LINE OPTIONS A script based on Test::Assertions::TestScript will detect the following command line options. -t Shallow tracing. Traces are "print"ed and AutoImport is turned on. -T Deep tracing. Traces are "print"ed and AutoImport is turned on. --trace-module=MODULE Imports tracing into MODULE specifically. Can be specified multiple times. -s Save generated output. You will need to write the actual code to do this in your testscript, but you can inspect $Test::Assertions::TestScript::SAVE_OUTPUT to see whether this argument was given. Be aware that all other command line options will be disregarded unless the "options" import parameter is used to capture them. VERSION
$Revision: 1.18 $ AUTHOR
Colin Robertson <cpan _at_ bbc _dot_ co _dot_ uk> COPYRIGHT
(c) BBC 2005-6. This program is free software; you can redistribute it and/or modify it under the GNU GPL. See the file COPYING in this distribution, or http://www.gnu.org/licenses/gpl.txt perl v5.10.0 2006-08-10 Test::Assertions::TestScript(3pm)
All times are GMT -4. The time now is 03:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy