Re: IGNITE-4404 long running test refactoring - how to refactor?

2017-02-27 Thread Дмитрий Рябов
I think we can keep this numbers for atomic behavior and decrease for transactional. But which tests can be replaced with mocks if they all use node's cache? 2017-02-22 12:47 GMT+03:00 Константин Дудков : > Answered to ticket. It's more about testing process than real refactoring > so I think we

Re: IGNITE-4404 long running test refactoring - how to refactor?

2017-02-22 Thread Константин Дудков
Answered to ticket. It's more about testing process than real refactoring so I think we need to discuss it further. 21.02.2017, 17:54, "Yakov Zhdanov" : > Konstantin Dudkov, you created ticket some time ago. Can you please clarify? > > --Yakov -- С уважением, Константин Дудков kdud...@ya.ru

Re: IGNITE-4404 long running test refactoring - how to refactor?

2017-02-21 Thread Yakov Zhdanov
Konstantin Dudkov, you created ticket some time ago. Can you please clarify? --Yakov

IGNITE-4404 long running test refactoring - how to refactor?

2017-02-21 Thread Дмитрий Рябов
Hello, community. Ticket description: in testTransform final int THREADS = 5; final int ITERATIONS_PER_THREAD = 10_000; So, what should I change? Other methods have final int THREADS = 5; final int ITERATIONS_PER_THREAD = iterations(); where iterations() {return 10_000;} Should I use iteratio