GitLab

Thanks @kirr . What's the plan to make a SlapOS profile to use on test suite in Nexedi ERP5 ? it could be a component/nxdtest/test.cfg profile similar to component/pygolang/test.cfg. If yes, do you also plan to move the nxdtest sections from stack to a component/nxdtest/buildout.cfg ?

@jerome, thanks for feedback. I was working on wendelin.core and suspected a bug on nxdtest side; did cd nxdtest and tried to run nxdtest (the same way I do to run wendelin.core tests all the time) and it said that there is no '.nxdtest'. The bug turned out to be in wendelin.core codebase - not nxdtest - but this is how this patch was born. Still I believe that having automatic test for testing infrastructure itself is good.

I did not thought about the plan yet, but moving to component/nxdtest/test.cfg seems reasonable. If you agree with this we could do.

Honestly I prefer to merge slapos!839 (merged) first and then proceed with this reworking. It is very time consuming on my side to run, gather, analyze that all the many failures are orthogonal to my changes and report tests status as in e.g. slapos!839 (comment 118948) and slapos!839 (comment 119275) as requested by @romain. Adding component/nxdtest rework would create the need to redo this verification. I frankly don't understand what is going on with that merge request because there is ~ 2 weeks selence after last rework and even though I pinged people ~ 1 week ago, there is no reply...

Thanks @kirr that seems a good plan, let's get slapos!839 (merged) merged first.

Thanks, @jerome. And thanks for pinging people on slapos!839 (merged).

mentioned in commit 549cc2f6

@jerome, slapos!839 (merged) was merged (thanks again for pinging people), so I've applied this patch to master as 549cc2f6.

Are you interested to do the component/nxdtest/test.cfg rework by yourself?

I do not insist, but if you are interested, that would help on my side as I'm currently hands down in getting wendelin.core 2 into shape.

Thanks beforehand,
Kirill

closed

Thanks @kirr I can not do this rework right now, but I'm planning to do it at the same time that adding unittest summary support, which will be required to finish porting SlapOS.Eggs.UnitTest-Master and SlapOS.SoftwareReleases.IntegrationTest. I might also be busy this end of year

@jerome, thanks for feedback. There is no hurry here. So if you could indeed do it - at the time which is convenient for you - along side SlapOS.Eggs.UnitTest-Master porting, that would be good. And good luck with getting your things done this year.

Test nxdtest via nxdtest