Feature #7820

Automatically test Pidgin

Added by intrigeri 2014-08-26 23:10:33 . Updated 2015-03-23 02:02:25 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Test suite
Target version:
Tails_1.3.1
Start date:
2014-10-05
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Instant Messaging
Deliverable for:

Description

Subtasks

Feature #8002: Automatic tests for XMPP in Pidgin Resolved

100
Feature #8001: Automatic tests for OTR in Pidgin Resolved

100
Feature #8003: Automatic tests for IRC in Pidgin Resolved

100
Feature #8966: Automatic tests for IRC CTCP in Pidgin Resolved

100

History

#1 Updated by intrigeri 2014-08-26 23:12:17

#2 Updated by intrigeri 2014-10-05 06:03:03

#3 Updated by intrigeri 2014-10-05 06:03:19

#4 Updated by intrigeri 2014-10-05 06:07:28

  • blocked by deleted (Feature #8001: Automatic tests for OTR in Pidgin)

#5 Updated by intrigeri 2014-10-05 06:07:32

  • blocked by deleted (Feature #8002: Automatic tests for XMPP in Pidgin)

#6 Updated by intrigeri 2014-10-20 14:08:01

  • blocks #8117 added

#7 Updated by anonym 2014-12-12 16:41:52

  • Target version changed from Tails_1.2.2 to Tails_1.2.3

#8 Updated by BitingBird 2015-01-07 18:10:55

  • Affected tool set to Instant Messaging

#9 Updated by anonym 2015-01-13 14:14:33

  • Target version changed from Tails_1.2.3 to Tails_1.3

#10 Updated by intrigeri 2015-02-23 14:17:16

  • Status changed from Confirmed to In Progress

#11 Updated by anonym 2015-02-24 20:04:05

  • Target version changed from Tails_1.3 to Tails_1.3.2

#12 Updated by anonym 2015-02-24 20:06:08

I’ve written (unpublished) an OTR-enabled (python-otr) XMPP bot (python-jabberbot) that will make the two child tickets very simply (at least compared to juggling two accounts in the same Tails session, whether that’s in one pidgin instance, or in two separate ones).

#13 Updated by sajolida 2015-02-26 15:13:06

I’m concerned to see that this ticket has been postponed for the fourth time. Take into account that this is blocking a funders’ deliverable (#8117) and cannot be postponed anymore this time. So marking this as Elevated.

#14 Updated by intrigeri 2015-03-15 09:23:14

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

Applied in changeset commit:feab4d87082542279d8b3595b79b80c6abe1d39b.

#15 Updated by intrigeri 2015-03-15 09:24:48

  • Status changed from Fix committed to In Progress

Ooops, I mistakenly marked this ticket as “fix committed” due to the erroneous branch name for Feature #8966.

#16 Updated by intrigeri 2015-03-17 11:49:27

  • Assignee changed from anonym to intrigeri
  • QA Check set to Ready for QA

#17 Updated by intrigeri 2015-03-17 12:04:25

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

Applied in changeset commit:ff9063e75d95029c454b763b4d6298dd802ec022.

#18 Updated by intrigeri 2015-03-17 12:13:33

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

Yay!

#19 Updated by BitingBird 2015-03-22 11:50:55

  • Target version changed from Tails_1.3.2 to Tails_1.3.1

#20 Updated by BitingBird 2015-03-23 02:02:26

  • Status changed from Fix committed to Resolved