8 Commits

Author	SHA1	Message	Date
vyzo	2dc46af415	update tests for quadratic p4	2020-05-08 21:20:04 +03:00
vyzo	076c6c1ab5	try to deflake MeshFailure test; travis managed to fail on this ... apparently creating the score object and calling refreshScores can take 500ms on travis!	2020-05-07 01:45:04 +03:00
vyzo	0832791d9c	extend behaviour penalty test to ensure coverage	2020-05-06 19:41:53 +03:00
vyzo	3cc169362f	incorporate p7 into score	2020-05-06 19:41:53 +03:00
vyzo	ae3a02f553	add test for rejections with ignore validator decision	2020-05-04 09:42:20 +03:00
vyzo	027234cdfa	add tests for message rejection paths	2020-04-27 18:35:25 +03:00
Yusef Napora	ac70e7e738	be less dependent on accurate time calculations in test ... thanks travis...	2020-04-23 22:00:08 +03:00
dirkmc	b2de9a56fe	Score tests (#288) ... * test: score time in mesh * add TestScoreFirstMessageDeliveries * rm redundant initialization to zero * add TestScoreFirstMessageDeliveriesCap * add TestScoreFirstMessageDeliveriesDecay * fix comment * add TestScoreMeshMessageDeliveries * comments * add TestScoreMeshFailurePenalty * add TestScoreInvalidMessageDeliveries also, TestScoreInvalidMessageDeliveriesDecay * add TestScoreApplicationScore * add TestScoreIPColocation * add TestScoreMeshMessageDeliveriesDecay * add TestScoreRetention * try longer interval for TimeInMesh test we seem to take longer to collect the score on travis, which causes the score to be outside the expected bounds. hopefully a longer wait time will give us more wiggle room. Co-authored-by: Yusef Napora <yusef@protocol.ai>	2020-04-23 13:03:52 -04:00