[Unit Testing Framework] Feedback

Forge Component
Published on 2018-01-11 by Paulo Ramos
32 votes
Published on 2018-01-11 by Paulo Ramos
First of all, congratulations. Your component is very well done and it was needed! :)

I'm trying to try it, but I'm having a compilation error:

Web Reference Integrity
Unable to access url 'http://localhost/utf_core/logging.asmx?wsdl' to verify if 'Logging' web reference is up-to-date.
Couldn't access resource at http://localhost/utf_core/logging.asmx?wsdl

Internal Error
Compilation Error.
Logging.asmx.cs(67,21): error CS1061: 'string' does not contain a definition for 'Request' and no extension method 'Request' accepting a first argument of type 'string' could be found (are you missing a using directive or an assembly reference?)
State: Second stage compilation

Do have any idea, why this is happening?

Updated: Forget it. I have reboot my computer, tried again, and it worked well. 

Thank you,


I tested it and it rocks :) very much needed and will benefit us quite well :)
Now get the Java version asap :)

Hi Andrew,

I've seen the dry-run of your presentation for NextStep and I would like to share with you some ideas:
- Coverage: it would be interesting to have a notion of coverage (how much of the action's execution nodes are executed) and how much of the actions are covered
- Error messaging for changes: what happens when you remove an action for which a test existed? What happens when you remove a test for an existent action?
- Performance monitoring: track the evolution of executing individual unit tests or all unit tests per action, and overall test suite.
- Execution history: when did the tests passes for the last time, how many runs were attempted
- Tests organization: for eSpaces with many tests there might be many unit tests which are difficult to find, pinpoint.

Looking forward to have a chance to personally discuss these items with you at NextStep!

good point, please discuss more

casino online