yeah, i will
чт, 9 февр. 2017 г. в 0:01, Denis Magda :
> > How could they co-exist ? When you developing some ticket you are risking
> > introduce bug which is reproduced by already failed test(s).
>
> Because there is no IT project that is bug-free. In my experience, it’s a
> usual situation whe
> How could they co-exist ? When you developing some ticket you are risking
> introduce bug which is reproduced by already failed test(s).
Because there is no IT project that is bug-free. In my experience, it’s a usual
situation when a part of the system is being evolved while the other is being
I also agree. I think we should create tickets for all failing tests and
have the community grab them.
On Wed, Feb 8, 2017 at 5:50 AM, Александр Меньшиков
wrote:
> +1 to Aleksey, Alexander and Vyacheslav.
>
> I suppose that the best option is make issue for every master-failed-test.
> And fix th
+1 to Aleksey, Alexander and Vyacheslav.
I suppose that the best option is make issue for every master-failed-test.
And fix them all.
Floating tests should be normal. I think in most case we can just add
repeating.
All new test for some not ready future should be marked like "Should be fix
in IG
I vote for the master-branche without failed-tests)
I understand that impossible to make it quickly.
We shall aim at this approach.
It will be more comfortable to us to develop.
2017-02-08 12:17 GMT+03:00 Alexander Fedotov :
> Hi,
>
> I would agree with Aleksey.
> From the CI perspective, fail
Hi,
I would agree with Aleksey.
>From the CI perspective, failing tests should be the main concern, because
it prevents a durable development of new features. Also, as Aleksey has
noted, developers working on different features could end up fixing the
same regressions, chances are - in different w
How could they co-exist ? When you developing some ticket you are risking
introduce bug which is reproduced by already failed test(s).
Moreover its time consuming to look up new failed tests when your build has
completed.
The last one, committers who introduced new bugs is responsible for them
and
Aleksey,
Bugs fixing and features development are two processes that usually co-exist.
Some of the committer/contributors fix tests/functionality while the others add
new functionality. Someone does both.
You’re welcomed to start fixing the failing tests. Are there any specific that
annoys you
