11 Commits (45b6b95d446f63a8b9159961e5f5b3810ce2f8fd)

Author	SHA1	Message	Date
Michael Telatynski	6ad31fe023	30 test failures to go :D	2019-12-16 11:12:48 +00:00
Stephen Solka	c3185a4cdb	breaking changes from expect upgrade ... Signed-off-by: Stephen Solka <stephen0q@gmail.com>	2019-01-02 16:59:48 -06:00
Luke Barnard	15bd2e157f	Test everything	2018-07-05 14:55:29 +01:00
Luke Barnard	d53c836fd7	Implement aggregation by error type for tracked decryption failures	2018-07-05 13:54:44 +01:00
Luke Barnard	01dd387970	Track UISIs in bulk ... Piwik supports sending an event value, which we can use to indicate cardinality of UISIs to be tracked instead of tracking them individually. This means we can track them at a lower frequency of (fairly arbitrary) 60s.	2018-06-28 15:07:27 +01:00
Luke Barnard	488cc416cf	For now, shelve persistance across sessions	2018-06-15 17:08:11 +01:00
Luke Barnard	c5252be4a8	Test everything, not just DFT	2018-06-15 16:51:11 +01:00
Luke Barnard	f08274585e	Persist tracked event ID hash using localStorage	2018-06-15 15:30:54 +01:00
Luke Barnard	011154396c	Add extra, useful expectation to test	2018-06-15 15:15:48 +01:00
Luke Barnard	ac0416af96	Do not track previously tracked failures	2018-06-15 14:48:20 +01:00
Luke Barnard	62601d657d	Implement DecryptionFailureTracker for less agressive tracking ... Instead of pinging Analytics once per failed decryption, add the failure to a list of failures and after a grace period, add it to a FIFO for tracking. On an interval, track a single failure from the FIFO.	2018-06-15 13:42:18 +01:00