gisce/destral

PowERP testing framework

Destral testing library

A library to do tests with our OpenERP Server (v5)

Note

The API is not stable, and can be changed.

Code as if the next guy to maintain your code is a homicidal maniac who knows where you live.

—Kathy Sierra and Bert Bates

destral's Issues

Set admin password using no-dropdb

When using --no-drodb the user admin is initialized without password.

Check undefined permissions

Raise error if no permissions are defined

approach use a new db for each module

When tests of different modules are passed, the db is reused for each one, sometimes it can lead to problems in the tests because another module has extended or modified the scheme of some tables

test_translate_modules doesn't work

Please could you take a look at https://drone.gisce.net/gisce/erp/5020

Especially to:

2017-07-03 09:15:29,584:INFO:destral.utils.compare_pofiles:Could not get po/pot file: /drone/src/github.com/gisce/erp/server/bin/addons/giscedata_perfils/i18n/[.po

AssertionError: There are -1 missing strings in the PO file of the module giscedata_perfils

But maybe is a testing suite configuration problem.

Boolean fields must be initialized

Show untranslated string

After #73 we need to show which are the missing strings

Allow multiprocess on destral execute

Execute destral with multiprocess on 1 process:

1. Create a multiprocessing pool
2. Queue destral for each affected module
3. Run the queued processes with multiprocessing

• On Circle-CI only 1 process, so the output won't be messed up
• Without attending Output, we could multi-process it
• The return value of the multiprocesses would be the JUnit so we can get all the data from those runs

PROS:

• No python imports on vars would be affected on multi-module tests
• No DB side-effects on multi-module tests (each run would have a new DB)

If a migration file is modified run the migration for that version

• Run code with the previous version to migrate
• Upgrade code
• Upgrade versions
• Upgrade db (running the scripts)

Force to use an existing database

With an environment variable DESTRAL_FORCE_DATABASE then use this database and not deleting it when the test is finished.

Let define which tests run

• Move to use click

It takes a lot of time to install tested modules when, may be, it is not required.

I am not sure if this is possible, but each time a test run starts it installs the module and all their dependencies, when may be it is not required when the database already exists. This is takes a lot of time and makes unit testing tedious.

I tried commenting line 51 (self.openerp.install_module(self.config['module'])) and the speed improvement is huge!

I propose two possible solutions that:

• Be more smart installing the module only when it is necessary (I am not really sure this is really possible).
• Add an environment variable or paramter to disable installation of the module showing a warning so developer knows it is disabled.

Mamba alternative

Mamba, the test runner, is discontinued (no compatibilitat with python >= 3.8)
nestorsalceda/mamba#143

So we have to considerate unittest, pytest...

Test migration script has migrate callable

To ensure https://github.com/gisce/erp/pull/3484

Fix always fails with reports

Generated POT in tests contains strings from other modules

When testing the module "base_extended", the .pot file generated in the test contains strings from module "base" and it should only contain strings from "base_extended"; like the .pot file generated from the ERP (Administration->Translations->Import/Export...).

Same with giscedata_ot_facturacio and giscedata_ot

Geneate Junit XML results

Circle CI supports tests metadata which inform the failed tests, slower tests, etc.

This metada uses Junit XML format

We have two options:

• Use python-junit-xml to generate the XML and use the API of Unittest to create the objects
• Integrate with library py.test which already supports Junit XML files

Test diferent views versions

https://github.com/gisce/erp/pull/13829

It's ok if a module has no translations?

You can see at https://github.com/gisce/erp/pull/4841

Check reports

If we have demo data check all the reports defined in the module with that demo data

Multi-module test crashes

Bug Found

• When you try to test multiple modules on the same execution, the Destral crashes after finish the first module test and start the next one.
• The stack trace of the error is the following one:
  

Database per TestSuite

When test_all_views fails dropdb

When module haven't got tests, dropdb after test_all_views fails

Allow when creating a Transaction() use PatchedCursor

For now if we want to patch the creation of new cursors inside a test we have to do:

with Transaction().start(self.database) as txn:
    with PatchNewCursors():
        ...

Maybe we can add the possibillity in creation a new Transaction to define to use PatchedCursors as

with Transaction(same_cursor=True).start(self.database) as txn:
    ...

Disable cron

Add mamba support

Find if spec directory is found and then run mamba suite

Check translations

Force the translation of all the strings from a module

Integration with pycodestyle

Integration with https://github.com/PyCQA/pycodestyle