Feature #7563: Update the automated test suite for Jessie ISO images
The I2P AppArmor confinement test case succeeds even when I2P is not confined
During the 2.0~rc1 test suite run, "Scenario: I2P's AppArmor profile is in enforce mode" apparently passed, while it should have noticed that on current Tails/Jessie, I2P is not confined (#10925).
I'm assuming that this test was verified to actually work when it was first implemented and merged (a033ba69, c2c96e76), and that this is a regression on Jessie, hence the parent task + assignee I'm setting.
Fix typo which have broken our AppArmor checks.
This `assert` will always pass since `mode` always is either one of
two String:s. The intention was clearly `assert_equal`.
#3 Updated by anonym over 3 years ago
- Assignee changed from anonym to kytv
- % Done changed from 0 to 50
- QA Check set to Ready for QA
- Feature Branch set to test/10926-fix-apparmor-check
By looking at the '
the running process "(.+)" is confined with AppArmor in (complain|enforce) mode' step I can immediately tell that it's incorrect:
modeis a String, so
assert(which only triggers on
nil) always passes. Obviously we want
So, yeah, anti-tests and all that.