"python unittests.py -uroot -D dbtests" doesn't work

Bug #899666 reported by Sandro Tosi on 2011-12-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Connector/Python
Confirmed
Low
Geert JM Vanderkelen

Bug Description

Hello,
In unittests.py (0.3.2) there's written:

Examples:
 Setting the MySQL account for running tests
 shell> python unittests.py -uroot -D dbtests

but:

$ python unittests.py -uroot -D dbtests
Usage: unittests.py [options]

unittests.py: error: no such option: -u

Cheers,
Sandro

Sandro Tosi (morph-debian) wrote :

neither -d works

There are indeed old docs in unittest.py. We'll address that.
unittests.py bootstraps its own MySQL server instance now, thus not using an existing one.

Full options are like this:

$ python unittests.py --help
Usage: unittests.py [options]

Options:
  -h, --help show this help message and exit
  -t NAME, --test=NAME Tests to execute, one of ['utils', 'protocol',
                        'constants', 'conversion', 'connection', 'cursor',
                        'pep249', 'bugs', 'examples', 'mysql_datatypes']
  -l NAME, --log=NAME Log file location (if not given, logging is disabled)
  --force Remove previous MySQL test installation.
  --keep Keep MySQL installation (i.e. for debugging)
  --debug Show/Log debugging messages
  --verbosity=NUMBER Verbosity of unittests (default 0)
  --mysql-basedir=NAME Where MySQL is installed. This is used to bootstrap
                        and run a MySQL server which is used for unittesting
                        only.
  --mysql-topdir=NAME Where to bootstrap the new MySQL instance for testing.
                        Defaults to current ./mysql_myconnpy
  --bind-address=NAME IP address to bind to
  -P NUMBER, --port=NUMBER
                        Port to use for TCP/IP connections.

Changed in myconnpy:
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → Geert JM Vanderkelen (geertjmvdk)
Sandro Tosi (morph-debian) wrote :

I see you're now trying to setup a complete new instance of MySQL, but that kinda makes testing the module (at least when building the package) a bit harder: would you consider adding the possibility to use an already running instance of MySQL too?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers