search

shekharpro / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

Reduce stack trace depth and adopt asynchronous testing pattern #412

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Debugging in MbUnit v3 is slower than in v2.4 because the stack trace depth
is significantly greater.  If we replace the current nested action-based
mechanism for compositing test behaviors with a chain of responsibility,
then the stack depth should be significantly reduced.

Using a chain of responsibility will also enable us to introduce
asynchronous evaluation of parts of tests so that long-running
(integration) tests can be broken down into series of asynchronous tasks
that go to sleep for some time then reawaken to complete processing later.

Original issue reported on code.google.com by jeff.br...@gmail.com on 26 Mar 2009 at 7:01

GoogleCodeExporter commented 8 years ago

Original comment by jeff.br...@gmail.com on 29 Jun 2009 at 8:33

GoogleCodeExporter commented 8 years ago 
Slipping to v3.2.  This is going to be a lot of work.

Original comment by jeff.br...@gmail.com on 18 Jul 2009 at 5:25

GoogleCodeExporter commented 8 years ago

Original comment by Yann.Tre...@gmail.com on 17 Jul 2010 at 8:20

GoogleCodeExporter commented 8 years ago

Original comment by Yann.Tre...@gmail.com on 14 Jun 2011 at 5:53