Finally, we have a working, if incomplete, set of unit tests in our
project. Thanks, Saggi (and others!).
Every module should have comprehensive unit tests. Writing good unit
tests can be hard, and writing testable code is even harder. However, I
would like to request that every new module, and ev
- Original Message -
> Finally, we have a working, if incomplete, set of unit tests in our
> project. Thanks, Saggi (and others!).
>
> Every module should have comprehensive unit tests. Writing good unit
> tests can be hard, and writing testable code is even harder. However,
> I
> would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/16/2012 09:15 AM, Dan Kenigsberg wrote:
> Finally, we have a working, if incomplete, set of unit tests in our
> project. Thanks, Saggi (and others!).
>
> Every module should have comprehensive unit tests. Writing good unit
> tests can be hard, a
I sending it on the list as well so everyone are aware of this.
I have a gdbinit with some custom actions for python
https://github.com/ficoos/gdb-python-scripts
`pystack` to print the python stack.
You got to have python-debuginfo for it to work.
I would love to get more features is but I don't
Hi,
While developing the REST API I was having trouble using the
getAllTasks(Info|Statuses) API to get tasks information. I found out that hsm
is hard-coding a tagged search for 'spm' in the calls to the task manager. Is
there a reason that this tag must be hard-coded or can we remove it as in t
