JC-1748 fix autotest
Merge pull request #9 from Dantalia/JC-1748FixAutotests

JC-1748 fix autotest
BBCodeTest

tests with dataProvider
Merge pull request #10 from pavelgradobik/master

BBCodeTest
Fixed compilation errors in BbCodeTest.
Updated BB Code tests to be more informative. And made them pass.

- While test was expecting a validation error, it was not handling exceptions
 from WebDriver layer and therefore it would fail. Added exception handling.
- Added a logging of the case that fails - previously if the test fails, nothing
 would be logged.
- Topics that are created while test execution now have a meaningful part in
 their title so that it's easier to distinguish them if they fail and you watch
 a video record. Also random part was added so that titles differ.
Added BB Code tests to the run, previously they were not added to the config.
Updated the filename of the BbCodeTest.java to match the class name
Optimizing topic creation tests: removed waits when marking topic as sticked.

This is done because most of the time we don't have that checkbox present on
the page but Selenium still waits for implicit timeout (10 secs) for it to show
up. Because of that we spend 20 secs just to wait for Announcement & Sticked
checkboxes to appear, but this never happens. Therefore updated the code
that created the topic not to wait for these checkboxes if they are not on the
page RIGHT NOW.
This might sound dangerous since there might be cases when we'd like to check
the correct work of permissions - whether they impact showing of checkboxes
or not, but I think we'd need some other ways to check that - the price of
these tests is too high.
Fixed errors in the BB Code test cases, they had typos like [/qindent], etc.

Also fixed the error messages when tests fail, they were wrong at some
places.
Added checks in BB code tests on whether previous test left us on topic creation page.

Since it's possible that the test fails and leaves us on the topic creation page and then
next test tries to open main page, we can get into a situation when browser asks us
whether we really want to leave the page (prev test entered some data). This means
that all the tests fail afterwards since they can't make the browser leave the topic
creation page. So current fix checks on the test start whether
Updated [code] bb code tests since they were actually putting [size=] instead of [code].
Updated BeforeMethod of BB Code Tests to handle UnsupportedOperationException
when working with alerts since some browsers (like mobile, htmlunit) don't
support alerts.
Updated handling of alerts in BB code tests, exceptions were thrown not as-is (UnsupportedOperationException), but as a WebDriverException with root cause as UnsupportedOperationException.
Disabled BB Code Tests since they are not yet ready to be run on continuous basis.

Additionally updated some test cases on max length because their expectations
were wrong.
Updated BB Code related cases - removed duplicates, updated max boundary tests.

- Max boundary is calculated by the total number of symbols posted, not by
 text symbols only. This means that bb codes also should be taken into account.
- Additionally optimized filling of post body by WebDriver Layer - previously
it was sending the whole 20K of symbols in one go, but that hangs the browser
therefore it was changed to split the body into small portions.
Disabled BB Code Tests since they are not passing yet (tests per se are not ideal yet).
Switched of BB Codes Tests again to see how what of them are failing on CI.
Updated dependencies so that w3c validation can initialize logger normally.

Note, that some dependencies were declared directly in sub-modules which
is not quite right - all deps should be declared in `<dependencyManagement>`
and only then added to a particular sub-module.
BB Code Test threw NPE sometimes when working with alerts, got rid of that situation.