- pass around the assertion_report to the YAML importer
- removed TestReport, which was identical to assertion_report
- assertion_report is simpler (no more severity level)
- use the report to log a greppable sentence when some test failed.
Previously the runbot had to grep for a Traceback which was an
unreliable technique (e.g. an exception can be purposefuly
generated as part of a test and the associated traceback
visible in the logs). Now it can grep
"At least one test failed when loading the modules".
bzr revid: vmt@openerp.com-20120302110227-nqrl7i46ju28ntdr
- moved a few YAML tests to unittest2 for demonstration purpose
- changed --test-disable to --test-enable (and swapped its meaning)
bzr revid: vmt@openerp.com-20120301134608-szuktuj8imdhmn0r
OpenERP depends on PostgreSQL 8.3 so we can now
use 'IF EXISTS'. It's also necessary to 'CASCADE'
the drop, otherwise depending views will prevent
the deletion and thus update of the view.
Depending views will automatically be updated
later and thus re-created, so this is safe.
bzr revid: odo@openerp.com-20120227165737-z5fgb6fle9g0cylw
The processing of <report> tags during XML file
processing is not modular or extensible, which
means that extra reporting engines cannot easily
add custom behavior for <report> records of their
type. By returning the newly created ID in
the tag_report() method we at least allow them
to hook up a monkey-patch without need to copy-
paste the original code.
This patch also allows an extra XML attribute
for webkit headers, because the original @header
attribute is reserved for a boolean value.
bzr revid: odo@openerp.com-20120214135255-a7hyxsoif4jhg6ro
The GetText spec says that PO auto-comments indicating
the source location have this form:
#: /path/to/file:lineno
However OpenERP's POT export system defaults to a modified
version of this format with an extra 'type' field:
#: type:/path/to/file:lineno
The babel extractors we use for openerp-web's translations
have the GetText format hardcoded, so it's a good idea
to be more lenient and allow the standards annotations too.
We can use a default 'code' type for such cases.
For openerp-web translations the type does not matter,
as the translations will be directly loaded by the
web engine from the PO files and served in Javascript
to the browser, with no typing needed.
This patch simply avoids failing to parse updated PO files
that will contain standard GetText annotations for the
openerp-web related terms.
bzr revid: odo@openerp.com-20120202143210-05p1w24t6u77cyv8
Warnings are handled with the other logs (and not always sent to stderr),
they also appear under a module __name__ channel instead of py.warn.
The disadvantage is that there is no longer specific warnings,
such as pending deprecation warning or deprecation warning.
bzr revid: vmt@openerp.com-20120125132407-u33idc0qh7ecs1i5
Fabien Pinckaers