Move fuzzer under s3tests/fuzz.

This way, its unit tests are separate from s3tests/functional,
and s3tests/functional is the thing that actually talks to an
S3 implementation over the wire.

To actually run the fuzzer, use ./virtualenv/bin/s3tests-fuzz-headers
This commit is contained in:
Tommi Virtanen 2011-10-13 13:34:23 -07:00
parent a18eee85fe
commit 27d2e40b7d
5 changed files with 5 additions and 5 deletions

0
s3tests/fuzz/__init__.py Normal file
View file

View file

@ -3,7 +3,7 @@ from boto.exception import BotoServerError
from boto.s3.key import Key
from httplib import BadStatusLine
from optparse import OptionParser
from . import common
from .. import common
import traceback
import itertools

View file

View file

@ -1,17 +1,17 @@
mport sys
import sys
import itertools
import nose
import random
import string
import yaml
from s3tests.fuzz_headers import *
from ..headers import *
from nose.tools import eq_ as eq
from nose.tools import assert_true
from nose.plugins.attrib import attr
from .utils import assert_raises
from ...functional.utils import assert_raises
_decision_graph = {}

View file

@ -25,7 +25,7 @@ setup(
's3tests-generate-objects = s3tests.generate_objects:main',
's3tests-test-readwrite = s3tests.readwrite:main',
's3tests-test-roundtrip = s3tests.roundtrip:main',
's3tests-fuzz-headers = s3tests.fuzz_headers:main',
's3tests-fuzz-headers = s3tests.fuzz.headers:main',
],
},