Re: Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Александр Меньшиков
Hi Dmitry, You are right this is not a sorting, this is a ranking by two parameters where both of them equal in priority. For such task in math, we have an idea of "dominating subset". It simply too understand by example: P1, P2 E1 2, 2 E2 1, 2 E3 2, 1 E4 1, 1 Here element E1 dominate a

Re: Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Dmitry Pavlov
Hi Alexander, I did not quite understand how this list of top tests was obtained. It does not look like sorted. Can you clarify? Sincerely, Dmitriy Pavlov пн, 14 мая 2018 г. в 20:48, Александр Меньшиков : > Vyacheslav, > I have made a simple ranking for your data for highlighting classes which

Re: Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Александр Меньшиков
Vyacheslav, I have made a simple ranking for your data for highlighting classes which more than other needs testing. Please take a look at the list which I have done (36 classes): https://drive.google.com/file/d/1RJrtnN77MeEWLTShFzqaLInCdOSb9WdC/view?usp=sharing Below you can read how did it in

Re: Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Александр Меньшиков
Hi Vyacheslav, Great job! I specifically happy to see jacoco.csv file into the archive. I think I can range classes by some complex criterion, like coverage/complexity. That classes could be the first in the queue for testing. 2018-05-14 17:49 GMT+03:00 Vyacheslav Daradur : > TestSuites weren't

Re: Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Vyacheslav Daradur
TestSuites weren't used. Set of tests classes was created as result of finding not abstract classes which names contain '*Test*' except '*TestCase*' in '/src/test/java/org/apache/ignite' as Maven does [1]. Each tests class was executed and covered separately. You can see used tests classes in th

Re: Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Dmitry Pavlov
Ok, thank you. I missed that I should download the archive first. I've found for example that method truncate in FSyncWalManager is not covered. Which test suites were executed? пн, 14 мая 2018 г. в 17:16, Vyacheslav Daradur : > Hi, Dmitry, > > Download and unpack the archive first: > > https:/

Re: Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Vyacheslav Daradur
Hi, Dmitry, Download and unpack the archive first: https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-tests-coverage-report-rev-d83f1ec.zip On Mon, May 14, 2018 at 5:12 PM, Dmitry Pavlov wrote: > Hi Vyacheslav, > > https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-t

Re: Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Dmitry Pavlov
Hi Vyacheslav, https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-tests-coverage-report-rev-d83f1ec.zip?dl=0&file_subpath=%2Fcoverage-report%2Findex.html says error 400 for me. Sincerely, Dmitriy Pavlov пн, 14 мая 2018 г. в 17:06, Vyacheslav Daradur : > Hi, Igniters! > > I’ve mad

Tests coverage report of Ignite 2.5 core module

2018-05-14 Thread Vyacheslav Daradur
Hi, Igniters! I’ve made tests coverage report of core module using Jacoco 0.8.1 I’d like to share results with the community. Here is a link: https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-tests-coverage-report-rev-d83f1ec.zip?dl=0 For viewing the report unpack the archive and