bitmask_thunderbird.git/tests/integration, branch 0.10rc1 [bitmask_thunderbird] [bug] replace content-type after removing the signature 2017-08-25T08:29:22+00:00 Ruben Pollan meskio@sindominio.net 2017-08-22T11:00:09+00:00 5292016becad94bfe603cdb7c4833b82ac07723a - Resolves: #9003 
- Resolves: #9003
[test] ca_cert_path can not be an empty string 2017-07-18T20:38:17+00:00 Ruben Pollan meskio@sindominio.net 2017-07-18T20:38:17+00:00 2b239d73868b69db083de517b26498b7888b3650 






[feat] push private key updates into nicknym
2017-06-12T18:34:15+00:00

Ruben Pollan
meskio@sindominio.net

2017-06-08T09:14:38+00:00

f0117969b19e05d568a108b12390c47a011576f6

Deal as well with sending key if key is outdated in the providers nicknym.

- Resolves: #8819, #8832





Deal as well with sending key if key is outdated in the providers nicknym.

- Resolves: #8819, #8832







[test] validate the CA cert fingerprint check
2017-06-05T17:42:13+00:00

Ruben Pollan
meskio@sindominio.net

2017-06-01T23:01:10+00:00

bc7dd3e575fcd5ed6ee6aa352c97741f761130aa












[bug] fail bonafide bootstrap for self sign certs
2017-06-05T17:42:13+00:00

Ruben Pollan
meskio@sindominio.net

2017-05-16T16:57:16+00:00

97774379834f0a06731093de54c986f8f7fd51a3

- Resolves: #8881





- Resolves: #8881







[tests] fix tests
2017-05-24T12:59:55+00:00

Kali Kaneko (leap communications)
kali@leap.se

2017-05-24T12:25:19+00:00

cf610930f7a9b56b0378920bfdd4263f490b5cb3












[tests] remove listener test
2017-05-16T17:28:39+00:00

Kali Kaneko (leap communications)
kali@leap.se

2017-05-15T14:42:28+00:00

b667facfe3c36e44396193a12748aaa9efbd718b

I've removed the add_listener method because it's not used anywhere.





I've removed the add_listener method because it's not used anywhere.







[bug] fix notification for incoming mail with several listeners registered
2017-05-16T17:28:35+00:00

Kali Kaneko (leap communications)
kali@leap.se

2017-04-27T13:20:24+00:00

c980cae46d101c0def23bf3398b65b2e0c614d2a

When setting the listeners in the IMAP Folder, we avoid setting more
than one listener for the same imap mailbox (because in some situations
we were registering way too many listeners).

this was making the pixelated inbox registering the notification and
therefore the imap mailbox not being registered.

this MR also refactors the way pixelated is initialized, so that it
avoid creating a second Account instance. In this way, we make sure that
the pixelated mua and the imap server share the same collections for a
given mailbox, and therefore any of the two is able to get a
notification whenever the other adds a message to the mailbox.

- Resolves: #8846, #8798





When setting the listeners in the IMAP Folder, we avoid setting more
than one listener for the same imap mailbox (because in some situations
we were registering way too many listeners).

this was making the pixelated inbox registering the notification and
therefore the imap mailbox not being registered.

this MR also refactors the way pixelated is initialized, so that it
avoid creating a second Account instance. In this way, we make sure that
the pixelated mua and the imap server share the same collections for a
given mailbox, and therefore any of the two is able to get a
notification whenever the other adds a message to the mailbox.

- Resolves: #8846, #8798







[tests] fix tests
2017-04-27T17:33:30+00:00

Kali Kaneko (leap communications)
kali@leap.se

2017-04-26T16:56:49+00:00

13760d78fba87570c91c0a2e702980d2ec45a0ed

mock a renamed method.





mock a renamed method.







[test] remove randomness tester
2017-04-03T13:45:53+00:00

Ruben Pollan
meskio@sindominio.net

2017-04-03T09:27:21+00:00

9883c75446187af0f88e03af75b42e8d3773fa18

There was a test in the Keymanager refresher that was testing the
randomness of the refreshing intervals. It was producing a bunch of
intervals and checking that all of them where different. This test
(rarelly) fails some times, but this is not a sign of bad randomness.

- Resolves: #8813





There was a test in the Keymanager refresher that was testing the
randomness of the refreshing intervals. It was producing a bunch of
intervals and checking that all of them where different. This test
(rarelly) fails some times, but this is not a sign of bad randomness.

- Resolves: #8813