view scripts/test/uuencode.test @ 833:98dc18ed57a3

uudecode test should just call "uudecode" (not multiplexer via a path), and first test shouldn't succeed if toybox isn't even there.
author Rob Landley <rob@landley.net>
date Wed, 27 Mar 2013 00:04:43 -0500
parents 1fdaba9a7124
children 3107c5525cc7
line wrap: on
line source

#!/bin/bash

[ -f testing.sh ] && . testing.sh

#testing "name" "command" "result" "infile" "stdin"

testing "uuencode not enough args [fail]" "uuencode 2>/dev/null" "" "" ""

testing "uuencode uu empty file" "uuencode test" \
	"begin 744 test\n\`\nend\n" "" "" 
testing "uuencode uu 1-char" "uuencode test" \
	"begin 744 test\n!80  \n\`\nend\n" "" "a" 
testing "uuencode uu 2-char" "uuencode test" \
	"begin 744 test\n\"86( \n\`\nend\n" "" "ab" 
testing "uuencode uu 3-char" "uuencode test" \
	"begin 744 test\n#86)C\n\`\nend\n" "" "abc" 

testing "uuencode b64 empty file" "uuencode -m test" \
	"begin-base64 744 test\n====\n" "" "" 
testing "uuencode b64 1-char" "uuencode -m test" \
	"begin-base64 744 test\nYQ==\n====\n" "" "a" 
testing "uuencode b64 2-char" "uuencode -m test" \
	"begin-base64 744 test\nYWI=\n====\n" "" "ab" 
testing "uuencode b64 3-char" "uuencode -m test" \
	"begin-base64 744 test\nYWJj\n====\n" "" "abc"