Hello,
Ildar Mulyukov writes:
> On 07.08.2009 02:23:14, Jan Hudec wrote:
> You could get test method names directly from the library. Use objdump
> for example.
NAK. I need to get the information about type relationships in the library.
Without the information from the .gir file, I would have
Hi, Jan!
On 07.08.2009 02:23:14, Jan Hudec wrote:
Option 1) The test code would be compiled to a library and a special
runner
program would use the .gir file to find test methods by their name
and create
and run test cases from them using the gobject-introspection library.
You cou
Hi Jan,
Pleased to see you took a look at our work.
2009/8/8 Jan Hudec
> Hello Julien,
>
> Julien Peeters writes:
> > We made work about that in LibGee. We wrote a TestFixture class which
> wraps
> > the TestCase class of GLib.Test namespace and make tests use Vala style
> > coding.
> >
> > Ou
Hello Julien,
Julien Peeters writes:
> We made work about that in LibGee. We wrote a TestFixture class which wraps
> the TestCase class of GLib.Test namespace and make tests use Vala style
> coding.
>
> Our work in only in the master branch of libgee (see tests/testfixture.vala)
> for the moment
Hello,
Julien Peeters writes:
> I'd like to add some enhancements like a better reporting, better assertion
> support with pretty printing, etc.. In that case effectively this framework
> may become an separate library. And, if contributors are interested in it,
> why not continuing to improve it
Hi Jan,
I'd like to add some enhancements like a better reporting, better assertion
support with pretty printing, etc.. In that case effectively this framework
may become an separate library. And, if contributors are interested in it,
why not continuing to improve it ? With your external runner fo
Hi Jan,
2009/8/6 Jan Hudec
> Julien Peeters writes:
> > We wrote a TestFixture class which wraps
> > the TestCase class of GLib.Test namespace and make tests use Vala style
> > coding.
> >
> > Our work in only in the master branch of libgee (see
> tests/testfixture.vala)
> > for the moment. I
Julien Peeters writes:
> We wrote a TestFixture class which wraps
> the TestCase class of GLib.Test namespace and make tests use Vala style
> coding.
>
> Our work in only in the master branch of libgee (see tests/testfixture.vala)
> for the moment. I have planned to improve this little framework
Frederik writes:
> Jan Hudec wrote:
> > The current binding for the testing framework has two disadvantages compared
> > to similar frameworks in other languages (C#, Java, Python, etc.)
> You might be interested in this:
> http://asabil.wordpress.com/2009/01/23/vala-and-unit-testing/
Thanks.
Tho
Hi Jan,
We made work about that in LibGee. We wrote a TestFixture class which wraps
the TestCase class of GLib.Test namespace and make tests use Vala style
coding.
Our work in only in the master branch of libgee (see tests/testfixture.vala)
for the moment. I have planned to improve this little fr
Jan Hudec wrote:
> Hello Folks,
>
> The current binding for the testing framework has two disadvantages compared
> to similar frameworks in other languages (C#, Java, Python, etc.)
You might be interested in this:
http://asabil.wordpress.com/2009/01/23/vala-and-unit-testing/
Best Regards,
Fred
Hello Folks,
The current binding for the testing framework has two disadvantages compared
to similar frameworks in other languages (C#, Java, Python, etc.):
- One has to manually add each test case.
- It's hard to actually use fixtures, because there is no GLib.Test.add or
GLib.Test.add_vtabl
12 matches
Mail list logo
