[ 
https://issues.apache.org/jira/browse/IGNITE-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738275#comment-16738275
 ] 

Oleg Ignatenko commented on IGNITE-10796:
-----------------------------------------

(i) Yet another thing I noticed after cleaning up as mentioned in prior comment 
is, there is something strange about {{ignoredOnly}} member value.

It looks like all testsuites except for two (more on these below) except this 
value to be always {{false}}. So far so good, okay...

Now, there are two suites that expect this value to be always {{true}}: 
IgniteIgnoredBinaryTestSuite and IgniteIgnoredBinarySimpleMapperTestSuite. This 
is also okay, except that the way how this value is set 
({{IgniteTestSuite.ignoreDefault(true)}}) would impact execution of all other 
suites in case if one of these happens to run in between these.

I re-checked with [~vozerov] who wrote mentioned suites per IGNITE-3980 and he 
suggests that undocumented assumption is that they are expected to be always 
executed separately from the rest. I plan to change code so that it is 
guaranteed that suites won't affect each other.

> Migrate from JUnit 3 to 4 suites involving IgniteTestSuite
> ----------------------------------------------------------
>
>                 Key: IGNITE-10796
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10796
>             Project: Ignite
>          Issue Type: Sub-task
>    Affects Versions: 2.8
>            Reporter: Oleg Ignatenko
>            Assignee: Oleg Ignatenko
>            Priority: Major
>
> This task is to migrate from JUnit 3 to 4 test suites suites involving 
> {{IgniteTestSuite}} API that was introduced per IGNITE-3658.
> If needed, refer parent task comments for more details.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to