Skip to content
This repository has been archived by the owner on Jan 14, 2019. It is now read-only.

Junit. Incorrect @step value processing #177

Closed
alert05 opened this issue Apr 4, 2014 · 3 comments
Closed

Junit. Incorrect @step value processing #177

alert05 opened this issue Apr 4, 2014 · 3 comments
Assignees
Labels
Milestone

Comments

@alert05
Copy link

alert05 commented Apr 4, 2014

If we use Russian symbols, we get some problem. For example, for step

    @Step("Ищем: query = {0}")
    public void searchFor(String query) {
        onTestPage().searchFor(query);
    }

we get xml report:
2092e0f2-3b31-47f6-99b0-0860e3791e23-testsuite xml 2014-04-04 12-57-11

and allure report:
allure dashboard 2014-04-04 12-51-58

@alert05
Copy link
Author

alert05 commented Apr 4, 2014

But for English sybols it's ok:

@Step("searchFor: query = {0}")

123

@alert05
Copy link
Author

alert05 commented Apr 4, 2014

And the same problem at @Parameterized.Parameters:

   @Parameterized.Parameters(name = "[Search query]: {0}")
    public static Collection params() {
        return Arrays.asList(new Object[] {new String[]{"Синхрофазотрон"}, new String[]{"Аллюр"}});
    }

we get
1234

@baev baev added the bug label Apr 4, 2014
@baev baev added this to the 1.3.5 milestone Apr 4, 2014
@baev baev self-assigned this Apr 4, 2014
@alert05
Copy link
Author

alert05 commented Apr 7, 2014

At the allure version 1.3.1 bug doesn't reproduce

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants