3 Commits

Author	SHA1	Message	Date
mooredan@suncup.net	b6768464af	A couple of small changes to the check collateral: ... - The script was looking for /root/.passwd-s3fs on my debian machine (it worked correctly on Ubuntu). Fixed the common.sh file to always look in the SUDO_USER's home directory - Added the passwd_file option to the s3fs command. Since the test runs as root, the $SUDO_USER's password file wasn't being looked for by the program itself. Instead the normal precedence was being followed and the /etc/passwd-s3fs file was being used. git-svn-id: http://s3fs.googlecode.com/svn/trunk@234 df820570-a93a-0410-bd06-b72b767a4274	2010-11-11 21:07:45 +00:00
apetresc	ec822185da	Usability improvement: use the ${SUDO_USER} environment provided by sudo to create the bucket based on the user who invoked the test using sudo. Much better this way. ... git-svn-id: http://s3fs.googlecode.com/svn/trunk@232 df820570-a93a-0410-bd06-b72b767a4274	2010-11-09 07:22:30 +00:00
apetresc	3022b87738	Added a simple integration test, and properly integrated it with autotools. ... To run integration tests, just use: sudo make check This will give you a report of all passes and failures. To add an integration test, just add it to the TESTS variable in s3fs/test/Makefile.am Make sure your test sources integration-test-common.sh and require-root.sh Having many of these for every feature will help us avoid regressions and develop with confidence. git-svn-id: http://s3fs.googlecode.com/svn/trunk@230 df820570-a93a-0410-bd06-b72b767a4274	2010-11-09 07:04:47 +00:00