Sponsored Content
Full Discussion: Test for file
Top Forums UNIX for Dummies Questions & Answers Test for file Post 97943 by bhargav on Friday 3rd of February 2006 11:31:29 AM
Old 02-03-2006
Code:
if ! test -f "file1"
then
   echo "file does not exist"
else
   echo "files does exist"
fi

 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the... (1 Reply)
Discussion started by: Max89
1 Replies

2. Shell Programming and Scripting

How to check weather a string is like test* or test* ot *test* in if condition

How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies

3. Shell Programming and Scripting

Problem in test file operator on a ufsdump archive file mount nfs

Hi, I would like to ask if someone know how to test a files if exist the file is a nfs mount ufsdump archive file.. i used the test operator -f -a h almost all test operator but i failed file1=ufs_root_image.dump || echo "files doesn't exist && exit 1 the false file1 is working but... (0 Replies)
Discussion started by: jao_madn
0 Replies

4. Shell Programming and Scripting

Prefixing test case methods with letter 'test'

Hi, I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
Discussion started by: royalibrahim
5 Replies

5. Shell Programming and Scripting

Hit multiple URL from a text file and store result in other test file

Hi, I have a problem where i have to hit multiple URL that are stored in a text file (input.txt) and save their output in different text file (output.txt) somewhat like : cat input.txt http://192.168.21.20:8080/PPUPS/international?NUmber=917875446856... (3 Replies)
Discussion started by: mukulverma2408
3 Replies

6. Shell Programming and Scripting

Test file

Hi, I try to test 3 files, #!/bin/bash if ; then echo "ok" else echo "ko" It works partially, but I want that the output tell me "ok" only if the three files doesn't exist. :b: (9 Replies)
Discussion started by: Arnaudh78
9 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 08:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy