[PR #348] [MERGED] Integration test summary, continue on error #1471

New issue

Closed

opened 2026-03-04 01:54:08 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:54:08 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/348
Author: @RobbKistler
Created: 2/5/2016
Status: ✅ Merged
Merged: 2/6/2016
Merged by: @ggtakec

Base: master ← Head: pushtests

📝 Commits (1)

7bfaa24 Integration test summary, continue on error

📊 Changes

4 files changed (+456 additions, -226 deletions)

View changed files

📝 test/integration-test-common.sh (+205 -10)
📝 test/integration-test-main.sh (+80 -137)
📝 test/small-integration-test.sh (+15 -79)
➕ test/test-utils.sh (+156 -0)

📄 Description

Details in README.md and s3fs-integration-test-common.sh

Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to
add test suites besides small-integration-test.sh that can test with various
s3fs options.

Each test run starts in a uniquely named at the top of the bucket. This allows
multiple runs against persistent storage without worrying about cleaning
up in error conditions that leave artifiacts behind.

Tests continues if a test case fails.

Results are summarized at the end of the test run

Environment variable to control debug level of s3fs-fuse

Environment variable to enable public bucket (makes it easier to poke
around with tools like curl)

Environment variable to start s3fs-fuse under valgrind

Environment variable that casues script sets up s3fs-fuse and then wait
indefinitely, making it easy to experiment manually with the mount
point.

Additional test case

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/348 **Author:** [@RobbKistler](https://github.com/RobbKistler) **Created:** 2/5/2016 **Status:** ✅ Merged **Merged:** 2/6/2016 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `pushtests` --- ### 📝 Commits (1) - [`7bfaa24`](https://github.com/s3fs-fuse/s3fs-fuse/commit/7bfaa24d252e99a59a7ec06004ab7eb38b52ea21) Integration test summary, continue on error ### 📊 Changes **4 files changed** (+456 additions, -226 deletions) <details> <summary>View changed files</summary> 📝 `test/integration-test-common.sh` (+205 -10) 📝 `test/integration-test-main.sh` (+80 -137) 📝 `test/small-integration-test.sh` (+15 -79) ➕ `test/test-utils.sh` (+156 -0) </details> ### 📄 Description Details in README.md and s3fs-integration-test-common.sh Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to add test suites besides small-integration-test.sh that can test with various s3fs options. Each test run starts in a uniquely named at the top of the bucket. This allows multiple runs against persistent storage without worrying about cleaning up in error conditions that leave artifiacts behind. Tests continues if a test case fails. Results are summarized at the end of the test run Environment variable to control debug level of s3fs-fuse Environment variable to enable public bucket (makes it easier to poke around with tools like curl) Environment variable to start s3fs-fuse under valgrind Environment variable that casues script sets up s3fs-fuse and then wait indefinitely, making it easy to experiment manually with the mount point. Additional test case --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>