StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POImporting functions from a shell script
primarykey
Id
12815774
data
AcceptedAnswerId
13350100
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-10T09:09:05.733
FavoriteCount
15
LastActivityDate
2018-07-02T08:30:42.867
LastEditDate
2012-10-10T15:18:14.930
LastEditorUserId
387981
OwnerUserId
387981
ParentId
0
PostTypeId
1
Score
36
ViewCount
28282
LastEditorDisplayName
text
Body
I have a shell script that I would like to test with shUnit. The script (and all the functions) are in a single file since it makes installation much easier. Example for <code>script.sh</code> <pre><code>#!/bin/sh foo () { ... } bar () { ... } code </code></pre> I wanted to write a second file (that does not need to be distributed and installed) to test the functions defined in <code>script.sh</code> Something like <code>run_tests.sh</code> <pre><code>#!/bin/sh . script.sh # Unit tests </code></pre> Now the problem lies in the <code>.</code> (or <code>source</code> in Bash). It does not only parse function definitions but also executes the code in the script. Since the script with no arguments does nothing bad I could <pre><code>. script.sh > /dev/null 2>&1 </code></pre> but I was wandering if there is a better way to achieve my goal. Edit My proposed workaround does not work in the case the sourced script calls <code>exit</code> so I have to trap the exit <pre><code>#!/bin/sh trap run_tests ERR EXIT run_tests() { ... } . script.sh </code></pre> The <code>run_tests</code> function is called but as soon as I redirect the output of the source command the functions in the script are not parsed and are not available in the trap handler This works but I get the output of <code>script.sh</code>: <pre><code>#!/bin/sh trap run_tests ERR EXIT run_tests() { function_defined_in_script_sh } . script.sh </code></pre> This does not print the output but I get an error that the function is not defined: <pre><code>#!/bin/sh trap run_tests ERR EXIT run_tests() { function_defined_in_script_sh } . script.sh | grep OUTPUT_THAT_DOES_NOT_EXISTS </code></pre> This does not print the output and the <code>run_tests</code> trap handler is not called at all: <pre><code>#!/bin/sh trap run_tests ERR EXIT run_tests() { function_defined_in_script_sh } . script.sh > /dev/null </code></pre>
Tags
<shell>
Title
Importing functions from a shell script
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMatteo
UserOwnerUserId
1. USMatteo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POImporting functions from a shell script
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POImporting functions from a shell script
 UserUserId
 USDocSalvager
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POImporting functions from a shell script
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.