Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_run_errors table is always empty... #16

Closed
JackieSproat opened this issue Sep 3, 2014 · 1 comment
Closed

test_run_errors table is always empty... #16

JackieSproat opened this issue Sep 3, 2014 · 1 comment

Comments

@JackieSproat
Copy link

output_2pass_2fail
log_2pass_2fail

When I execute the following commands:
$ python -m dbbot.run output_2pass_2fail.xml
$ sqlite3 robot_results.db
sqlite > .tables
sqlite > select * from test_run_errors;

test_run_errors appears to be empty???

I expected it to contain the 2 errors as shown in the log.html and screen shot of the output.xml file.

@JackieSproat
Copy link
Author

The "errors" I am interested are errors that result in test case failing.
Therefore, I modified
def _create_table_tests(self):
self._create_table('tests', {
'suite_id': 'INTEGER NOT NULL REFERENCES suites',
'xml_id': 'TEXT NOT NULL',
'name': 'TEXT NOT NULL',
'message' : 'TEXT', #ADDED by JACKIE
'timeout': 'TEXT',
'doc': 'TEXT'
}, ('suite_id', 'name'))
in database_writer.py
and
def _parse_test(self, test, test_run_id, suite_id):
self._verbose(' `--> Parsing test: %s' % test.name)
try:
test_id = self._db.insert('tests', {
'suite_id': suite_id,
'xml_id': test.id,
'name': test.name,
'message' : test.message, #ADDED by JACKIE
'timeout': test.timeout,
'doc': test.doc
})
in robot_results_parser.py
Now, all I have to do is get failbot working and i will have a database of test failure messages :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant