Xavier Morel 2ab06ca96b [IMP] *: require explicitly specifying whether exceptions in logs are valid ... Seems like a good idea to better keep track of the log of an Odoo used to testing, and avoid silently ignoring logged errors. - intercept odoo's stderr via a pipe, that way we can still write it back out and pytest is able to read & buffer it, pytest's capfd would not work correctly: it breaks output capturing (and printing on failure); and because of the way it hooks in it's unable to capture from subprocesses inheriting the standard stream, cf pytest-dev/pytest#4428 - update the env fixture to check that the odoo log doesn't have any exception on failure - make that check conditional on the `expect_log_errors` marker, this way we can mark tests for which we expect errors to be logged, and assert that that does happen		2024-06-12 15:09:42 +02:00
..
conftest.py	[IMP] *: store filestore & forwardport checkouts in temp dirs	2022-08-05 15:35:51 +02:00
test_batches.py	[REF] forwardport: update re_matches to not use a regex	2024-06-04 14:18:04 +02:00
test_conflicts.py	[IMP] *: require explicitly specifying whether exceptions in logs are valid	2024-06-12 15:09:42 +02:00
test_limit.py	[IMP] *: require explicitly specifying whether exceptions in logs are valid	2024-06-12 15:09:42 +02:00
test_overrides.py	[CHG] *: move forward-porting over to batches	2024-05-24 09:08:56 +02:00
test_simple.py	[IMP] forwardport: don't ping *every* forwardport	2024-06-10 18:47:49 +02:00
test_updates.py	[ADD] *: per-repository webhook secret	2024-06-06 11:07:57 +02:00
test_weird.py	[IMP] *: require explicitly specifying whether exceptions in logs are valid	2024-06-12 15:09:42 +02:00