Feature #14469
Write Gherkin scenarios for VeraCrypt automated tests
100%
Description
This is the initial part of “A.3 Write automated tests”. Actual steps will be implemented in Feature #14470, Feature #14471 and Feature #14472.
For potential scenario candidates, see:
- our end-user doc
- the scope of our work
- our UI design
Subtasks
Related issues
Blocked by Tails - |
Resolved | 2017-09-29 | |
Blocks Tails - |
Resolved | 2017-08-28 |
History
#1 Updated by intrigeri 2017-08-28 16:49:26
- Subject changed from Write Gherkin scenarios to Write Gherkin scenarios for VeraCrypt automated tests
- Category set to Test suite
#2 Updated by intrigeri 2017-09-29 17:15:09
- blocked by
Feature #14742: VeraCrypt: UX & GUI design sprint added
#3 Updated by intrigeri 2017-09-29 17:16:47
- Description updated
#4 Updated by intrigeri 2017-09-29 17:17:18
- blocks
Feature #14470: Write tests for VeraCrypt support in udisks added
#5 Updated by intrigeri 2017-09-29 17:17:26
- blocks
Feature #14471: Write tests for VeraCrypt support in GNOME Disks added
#6 Updated by intrigeri 2017-09-29 17:17:29
- blocks
Feature #14472: Write tests for VeraCrypt support in GNOME Files added
#7 Updated by anonym 2018-01-23 19:52:49
- Target version changed from Tails_3.5 to Tails_3.6
#8 Updated by anonym 2018-02-26 15:23:44
- blocked by deleted (
)Feature #14470: Write tests for VeraCrypt support in udisks
#9 Updated by anonym 2018-02-26 15:23:46
- blocked by deleted (
)Feature #14472: Write tests for VeraCrypt support in GNOME Files
#10 Updated by anonym 2018-02-26 15:23:49
- blocked by deleted (
)Feature #14471: Write tests for VeraCrypt support in GNOME Disks
#11 Updated by anonym 2018-02-26 15:25:41
- blocks
Feature #14471: Write tests for VeraCrypt support in GNOME Disks added
#12 Updated by anonym 2018-02-26 15:25:45
- blocks
Feature #14472: Write tests for VeraCrypt support in GNOME Files added
#13 Updated by intrigeri 2018-02-26 15:27:38
This can now be done for the GNOME Disks tests (Feature #14471). anonym will work on this during the 3.6 freeze.
#14 Updated by bertagaz 2018-03-14 11:32:17
- Target version changed from Tails_3.6 to Tails_3.7
#15 Updated by intrigeri 2018-03-28 09:25:03
- Priority changed from Normal to Elevated
#16 Updated by intrigeri 2018-05-07 14:06:21
- Target version changed from Tails_3.7 to Tails_3.8
#17 Updated by intrigeri 2018-05-25 13:20:37
- Target version changed from Tails_3.8 to Tails_3.9
#19 Updated by intrigeri 2018-06-26 17:15:21
- Assignee changed from anonym to intrigeri
- Target version changed from Tails_3.9 to Tails_3.10.1
#21 Updated by intrigeri 2018-09-12 08:47:36
- Feature Branch set to test/14471-veracrypt
#22 Updated by intrigeri 2018-09-12 08:50:17
- Description updated
#23 Updated by intrigeri 2018-09-12 09:15:24
- Description updated
#24 Updated by intrigeri 2018-09-12 20:46:24
- % Done changed from 0 to 10
#25 Updated by intrigeri 2018-09-12 20:46:52
- Status changed from Confirmed to In Progress
#26 Updated by intrigeri 2018-09-13 20:14:45
- Assignee changed from intrigeri to segfault
- % Done changed from 10 to 50
- QA Check set to Ready for QA
Gherkin written (and field-tested by actually implementing the scenarios). Interestingly, there was no budget allocated to review the VeraCrypt test suite work, not sure how it was supposed to be handled. Anyway, I figure you’re the best placed person to check whether what I’m testing makes sense, has good enough coverage (see Feature #14472#note-10), and is understandable. So please clock this review separately, as part of the “test suite maintenance” core budget.
Note that here I’m only asking for a review of the Gherkin i.e. the features/veracrypt.feature
file and nothing more. I’ll ask kibi to review the rest of my work once it’s ready.
#27 Updated by intrigeri 2018-09-18 14:44:16
- blocked by deleted (
)Feature #14472: Write tests for VeraCrypt support in GNOME Files
#28 Updated by segfault 2018-10-14 18:34:57
- Assignee changed from segfault to intrigeri
- QA Check changed from Ready for QA to Pass
Whoops, didn’t have this one on my radar. I took a look and the existing scenarios look good. I noticed that there are none for unlocking via GNOME Files (i.e. clicking on the entry in the places sidebar). I just read on Feature #14472 that that’s because you ran out of budget, so OK, the existing tests will have to do.
#29 Updated by intrigeri 2018-10-15 11:31:19
- Status changed from In Progress to Resolved
- Assignee deleted (
intrigeri) - % Done changed from 50 to 100
Thanks!