Bug #9355

More robust accessing the gpgApplet in the test suite

Added by kytv 2015-05-07 14:07:56 . Updated 2015-07-03 03:39:53 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Tails_1.4.1
Start date:
2015-05-07
Due date:
% Done:

100%

Feature Branch:
kytv:test/9355-more-robust-gpgapplet-accessing
Type of work:
Code
Blueprint:

Starter:
Affected tool:
OpenPGP Applet
Deliverable for:

Description

While working on Bug #9046 I found that in my nested VM set-up that the interactions with the gpgApplet can be fragile. The root cause seems to be the same as that in Bug #8928. I want to use the fix for Bug #8928 in the gpgApplet tests.

Subtasks

Related issues

Related to Tails - Bug #8928: "unclutter" can cause spurious errors with some configurations Resolved 2015-03-03
Blocks Tails - Bug #9046: Update the encryption test for Jessie Resolved 2015-03-11
Blocks Tails - Bug #9344: Sometimes Seahorse's Find keys dialog cannot be found during tests Resolved 2015-05-05

History

#1 Updated by kytv 2015-05-07 14:08:16

  • blocks Bug #9046: Update the encryption test for Jessie added

#2 Updated by kytv 2015-05-07 14:08:28

  • related to Bug #8928: "unclutter" can cause spurious errors with some configurations added

#3 Updated by kytv 2015-05-14 14:01:25

  • Status changed from New to In Progress

#4 Updated by kytv 2015-05-27 22:37:24

  • Assignee changed from kytv to anonym
  • % Done changed from 0 to 20
  • QA Check set to Ready for QA
  • Feature Branch set to kytv:test/9355-more-robust-gpgapplet-accessing

#5 Updated by kytv 2015-05-27 22:39:39

  • blocks Bug #9344: Sometimes Seahorse's Find keys dialog cannot be found during tests added

#6 Updated by anonym 2015-05-28 15:40:46

  • Assignee changed from anonym to kytv
  • QA Check changed from Ready for QA to Dev Needed

Ah, kytv:test/9344-seahorse-findkey is based on kytv:test/9355-more-robust-gpgapplet-accessing. Well, see my comment on Bug #9344 then, since it includes this one.

#7 Updated by anonym 2015-05-28 15:41:44

BTW, it would be good if you in the future made such relationship between branches/tickets very explicit.

#8 Updated by kytv 2015-05-28 16:44:01

anonym wrote:
> BTW, it would be good if you in the future made such relationship between branches/tickets very explicit.

I tried to do so with adding the “Blocked by” relationship though I suppose I should have explicitly mentioned it in the tickets’ comments.

#9 Updated by kytv 2015-05-28 18:57:50

  • Assignee changed from kytv to anonym
  • QA Check changed from Dev Needed to Ready for QA

Issues addressed and force pushed, otherwise the history would have been rather fugly.

#10 Updated by anonym 2015-06-02 11:48:43

  • Status changed from In Progress to Fix committed
  • % Done changed from 20 to 100

Applied in changeset commit:cd1daa20a8dd33af67d94fc4d0387b4b62ee6d21.

#11 Updated by anonym 2015-06-02 12:05:50

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

#12 Updated by intrigeri 2015-07-03 03:39:53

  • Status changed from Fix committed to Resolved