Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Roundup by @blake-mizerany sounds great, and I should make use of it in the future, but here is my "poor-man" approach for creating unit tests:</p> <ul> <li>Separate everything testable as a function.</li> <li>Move functions into an external file, say <code>functions.sh</code> and <code>source</code> it into the script. You can use <code>source `dirname $0`/functions.sh</code> for this purpose.</li> <li><p>At the end of <code>functions.sh</code>, embed your test cases in the below if condition:</p> <pre><code>if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then fi </code></pre></li> <li><p>Your tests are literal calls to the functions followed by simple checks for exit codes and variable values. I like to add a simple utility function like the below to make it easy to write:</p> <pre><code>function assertEquals() { msg=$1; shift expected=$1; shift actual=$1; shift if [ "$expected" != "$actual" ]; then echo "$msg EXPECTED=$expected ACTUAL=$actual" exit 2 fi } </code></pre></li> <li><p>Finally, run <code>functions.sh</code> directly to execute the tests.</p></li> </ul> <p>Here is a sample to show the approach:</p> <pre><code> #!/bin/bash function adder() { return $(($1+$2)) } ( [[ "${BASH_SOURCE[0]}" == "${0}" ]] || exit 0 function assertEquals() { msg=$1; shift expected=$1; shift actual=$1; shift /bin/echo -n "$msg: " if [ "$expected" != "$actual" ]; then echo "FAILED: EXPECTED=$expected ACTUAL=$actual" else echo PASSED fi } adder 2 3 assertEquals "adding two numbers" 5 $? ) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUnit testing for shell scripts
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAnthony Geoghegan
    1. USharidsv
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONice, thanks - I really like the structured programming approach to shell scripts.
      singulars
      1. PO
      1. USgareth_bowles
    2. COVery good observation there: 'Separate everything testable as a function'. It's important even if you don't (yet) write a test for it. It is a major factor in improving code readability. A couple of years back I started writing my (ksh) script according to this principle. Write everything as a function.
      singulars
      1. PO
      1. USHenk Langeveld
    3. CO@HenkLangeveld Won't the `exit 0` cause the "sourcee" (the one sourcing this) to exit as well? I think you are looking for `return` here.
      singulars
      1. PO
      1. USharidsv
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload