Project

General

Profile

Feature #956

Testing of signal emission is needed

Added by Marc Paterno over 8 years ago. Updated almost 2 years ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
-
Start date:
02/10/2011
Due date:
09/30/2013
% Done:

0%

Estimated time:
160.00 h
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration: 964

Description

Removing the emission of the postProcessEvent signal from the Schedule causes only one test to fail, and that test is not one that is directed at testing the signal emission feature.

We need to have test(s) that verify each signal is emitted at the right time.


Related issues

Related to art - Milestone #1091: Review all signal emission in the light of sentry considerations and exception safety.Accepted03/28/201109/30/2013

Related to art - Necessary Maintenance #946: Review and provide precise definitions of each signal watchpoint.Accepted02/08/201109/30/2013

History

#1 Updated by Walter E Brown almost 8 years ago

  • Status changed from New to Accepted

A recent bug that involved emitting a signal twice was only spotted because an entirely unrelated test happened to fail.

#2 Updated by Christopher Green about 6 years ago

  • Due date set to 09/30/2013
  • Category set to Infrastructure
  • Target version set to 1.09.00
  • Estimated time set to 160.00 h
  • Scope set to Internal
  • Experiment - added
  • SSI Package art added

Testing that each signal is called the expected number of times is relatively straightforward. However, the code is not structured currently to facilitate testing that each signal is called at the right time. It is far from clear how this could be done, but very clear that it will be extremely time-consuming to do.

#3 Updated by Christopher Green over 5 years ago

  • Target version changed from 1.09.00 to 521

#4 Updated by Kyle Knoepfel almost 2 years ago

  • Target version deleted (521)


Also available in: Atom PDF