On Sat, 8 Nov 2014, Robert Collins wrote:
What changes do you want to see in the ui?
I don't want to hijack the thread too much so I hope Dmitriy will join
back in but for me there are two aspects of the existing experience
that don't work out well. I suspect many of these situations can be
Hi guys,
Long time ago i've made patch [1] which added tests distribution between
processes and databases. It was simple py.test configuration which allows
us to reduce time of test execution almost linearly, on my local machine
one test run (distributed over 4 cores) takes 250 seconds.
At that
Hi Dmitry,
Thank you for bringing it up, it's not only about CI, it really takes
a lot of developers time to run Nailgun unit/integration tests on local
machine, and it's must have priority task in technical debt scope.
Personally I'm ok with py.test, but we should improve db creation mechanism
On Fri, 7 Nov 2014, Dmitriy Shulyak wrote:
As for testrepository - if you have positive experience using this tool,
share them, from my point of view it has very bad UX.
+1, but with the caveat that testr and its compatriots (e.g.
subunit) appear to have been optimized for automation of huge
What changes do you want to see in the ui?
On 7 Nov 2014 17:17, Chris Dent chd...@redhat.com wrote:
On Fri, 7 Nov 2014, Dmitriy Shulyak wrote:
As for testrepository - if you have positive experience using this tool,
share them, from my point of view it has very bad UX.
+1, but with the
