dkirillov/s3-tests
1
0
Fork 0
forked from TrueCloudLab/s3-tests
Code Pull requests Activity
Compatibility tests for S3 clones
666 commits 127 branches 0 tags 8.9 MiB
Python 100%
Find a file
Matt Benjamin 2d12e98ce0 boto3_s3tests: add tests for lifecycle expiration header 
The response to a successful PUT or HEAD (or GET) of/on
an object matching any enabled lifecycle expiration rule should
include an x-amz-expiration header for the object.  The
x-amz-expiration header consists of an expiry-date, rule-id tuple
indicating the earliest matching rule and the corresponding
expiration date for the object.

Also, while at it, add test for lifecycle expiration rule with
'Days' : 0, which should both apply and...work.

Signed-off-by: Matt Benjamin <mbenjamin@redhat.com>
2019-02-14 18:32:33 -05:00
s3tests s3tests: test copy objects (storage class) 2019-01-10 11:50:02 -08:00
s3tests_boto3 boto3_s3tests: add tests for lifecycle expiration header 2019-02-14 18:32:33 -05:00
.gitignore Say ".yaml" not ".yml". This is not MS-DOS, and YML is a Yahoo XML dialect. 2011-07-26 14:20:28 -07:00
bootstrap bootstrap: add libffi-dev for gevent 2018-05-30 16:36:54 +08:00
LICENSE MIT licensed. 2011-04-04 15:19:59 -07:00
README.rst boto3: Foundation laid for boto3 tests 2019-01-16 16:31:24 -05:00
request_decision_graph.yml fuzz: Write fuzzer rules for WebsiteConfiguration. 2015-06-14 22:11:42 -07:00
requirements.txt boto3: Foundation laid for boto3 tests 2019-01-16 16:31:24 -05:00
s3tests.conf.SAMPLE boto3: Foundation laid for boto3 tests 2019-01-16 16:31:24 -05:00
setup.py boto3: Foundation laid for boto3 tests 2019-01-16 16:31:24 -05:00
siege.conf dho-qa: Add siege config file and document running siege 2011-07-08 11:27:56 -07:00

README.rst 

========================
 S3 compatibility tests
========================

This is a set of unofficial Amazon AWS S3 compatibility
tests, that can be useful to people implementing software
that exposes an S3-like API. The tests use the Boto2 and Boto3 libraries.

The tests use the Nose test framework. To get started, ensure you have
the ``virtualenv`` software installed; e.g. on Debian/Ubuntu::

	sudo apt-get install python-virtualenv

and then run::

	./bootstrap

You will need to create a configuration file with the location of the
service and two different credentials. A sample configuration file named
``s3tests.conf.SAMPLE`` has been provided in this repo. This file can be
used to run the s3 tests on a Ceph cluster started with vstart.

Once you have that file copied and edited, you can run the tests with::

	S3TEST_CONF=your.conf ./virtualenv/bin/nosetests

You can specify which directory of tests to run::

	S3TEST_CONF=your.conf ./virtualenv/bin/nosetests s3tests.functional

You can specify which file of tests to run::

	S3TEST_CONF=your.conf ./virtualenv/bin/nosetests s3tests.functional.test_s3

You can specify which test to run::

	S3TEST_CONF=your.conf ./virtualenv/bin/nosetests s3tests.functional.test_s3:test_bucket_list_empty

To gather a list of tests being run, use the flags::

	 -v --collect-only

Some tests have attributes set based on their current reliability and
things like AWS not enforcing their spec stricly. You can filter tests
based on their attributes::

	S3TEST_CONF=aws.conf ./virtualenv/bin/nosetests -a '!fails_on_aws'

Most of the tests have both Boto3 and Boto2 versions. Tests written in
Boto2 are in the ``s3tests`` directory. Tests written in Boto3 are
located in the ``s3test_boto3`` directory.

You can run only the boto3 tests with::

        S3TEST_CONF=your.conf ./virtualenv/bin/nosetests -v -s -A 'not fails_on_rgw' s3tests_boto3.functional