unit test / run test in xfce code (here clipman)?
Sylvain Viart
sylvain at opensource-expert.com
Wed Dec 29 08:02:53 CET 2021
Hi Alex,
Thanks for your CC. :-)
On 27/12/2021 15:33, Alex wrote:
> in order that others can see what you did / to bring back you changes
> to the origin, it would help alot to have a merge request. Label it as
> WIP, if it is working in process.
>
> (Though currently xfce4-clipman-plugin is unmaintained, so dont expect
> a review / reply )
As my work was a PoC at first, it was not necessary to have a MR. Nor
even it have any meaning to me.
Also I didn't know the use-case of holding a change into a merge
request, that is still not to be merged.
Thanks for the information.
So I did a merge request for the work in progress:
https://gitlab.xfce.org/panel-plugins/xfce4-clipman-plugin/-/merge_requests/17
<https://gitlab.xfce.org/panel-plugins/xfce4-clipman-plugin/-/merge_requests/17>
reader useful link
https://docs.gitlab.com/ee/user/project/merge_requests/drafts.html
<https://docs.gitlab.com/ee/user/project/merge_requests/drafts.html>
current gitlab xfce version is: GitLab Community Edition 14.5.2
The new text label for WIP MR seems to be' Draft:'
Back on automated unit testing:
> > I mean if I've to run it [test binaries] manually, it's not the idea
> I've about an automated test suite.
>
> No idea what was the intend behind these tests ... a pity that ther
> was no README in the test-folder. Would be great if you could figure
> out and open an according MR.
>
> > So I suppose I can start anywhere...
>
> Yea, I think so. https://docs.gtk.org/glib/testing.html
> <https://docs.gtk.org/glib/testing.html> and automake probably are the
> right points to start looking.
Unfortunately the glib's forum/discourse answer was:
https://discourse.gnome.org/t/add-unit-testing-to-a-gtk-c-application/8450
<https://discourse.gnome.org/t/add-unit-testing-to-a-gtk-c-application/8450>
TL;DR: use meson not autotools 🙁
So setuping those automated test (glib one with automake) seems a bit
deprecated. They even removed the files mentioned is the doc from the
repos. 🙁
So I may start somewhere else. I will explore. 😕
This mean that setuping automated test will be a real quest (a huge
one), I'm gonna write a novel. 😉
It seems I found a thread with huge bobbin. 😁
Hopefully I'm very tenacious (some may say pugnacious, or even stubborn)
so I will go through.
Could the path of migrating from autotools to meson a valid one?
I mean I looked to some project in xfce, I even did a find search on the
docker container xfce-test /git and the only project using meson is
(over 65 repos)
./Greybird/meson.build
Note I don't know meson yet, nor autotools.
> > I also found: xfce-test and behave, but I don't know yet how to use it.
>
> Here some info: https://wiki.xfce.org/testing/xfce-test
>
Ho, thanks, it seems I missed this one.
To be continued.
Regards,
Sylvain.
--
Sylvain Viart - GNU/Linux Sysadmin/Developer/DevOps - France
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.xfce.org/pipermail/xfce4-dev/attachments/20211229/f408d354/attachment.html>
More information about the Xfce4-dev
mailing list