Commit 21aec2fd authored by Tails developers's avatar Tails developers

Clarify next steps, the discussion happened already, time to make it real.

parent 19197840
......@@ -3,9 +3,11 @@ suite would properly detect failure. Our manual erase memory test
procedure is a good example thereof: it checks that we *can* find the
pattern in memory if we skip the memory wipe step on purpose.
* Do we need an anti-test for non-IP packets in
* [[!taglink todo/code]] the anti-test of checking that, without
erasing memory, we can retrieve the known pattern. Just as we [[do
manually|contribute/release_process/test/erase_memory_on_shutdown]].
* [[!tag todo/discuss]] if we need an anti-test for non-IP packets in
`firewall_leaks.feature`? Does it even make sense? After all, so
far we've only cared about leaks to the Internet. What non-IP
packets can leak to the Internet?
[[!tag todo/discuss]]
......@@ -11,28 +11,9 @@ anonym after which the manual test can be removed:
* check that `memlockd` is running
# Discussion
# Tests that need fixing
The following test was tagged (in commit 3391f56) in an unexplained way:
* Testing that the needed files are really mapped in memory, and the
erasing process actually works, involves a more complicated
process that is worth [[a dedicated page|contribute/release_process/test/erase_memory_on_shutdown]].
`[needs-fix: erase_memory]` ([[todo/test_suite:_anti-tests]])
> What anti-tests are missing?
>> The anti-test of checking that, without erasing memory, we can
>> retrieve the known pattern. Just as we
>> [[do manually|contribute/test/erase_memory_on_shutdown]].
> The linked ticket mentions nothing relevant, but rather mentions
> that `erase_memory.feature` "is a good example thereof".
>> No. It says that our "**manual** erase memory test procedure is
>> a good example thereof". --intrigeri
[[!tag todo/discuss]]
See [[todo/test_suite:_anti_tests]].
# Related tickets
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment