Red doesn't expand columns of robot file in "Test Cases" view

[BeastModeActivated]

RED doesn't allow to expand the column in Test Case view. We pass all test case input as a list and group them in cells. But editing them in RED is very tough as it doesn't expand them.

Whereas columns are expanded automatically in RIDE.

File format we use is .robot

I have attached one snapshot to highlight this difference.

Kindly check.

[KrzysztofJozefowicz]

Hi
This is a know issue, indeed RED does not automatically add new column when number of columns are over default value. This is due philosophy that there should be sane number of arguments to keyword passed to have a decent readability so we intentionally does not add new column while working in table editors.
To overcome this, you have multiple options:

1. set default number of columns in Window-Preferences->RobotFramework-Editor - default value is 5 columns
2. go to source,add as many items separated by separators, for instance
   #comment line1 line2 line3 line4 line5 line6 line7 line8 line9 line10
   this can also help to add meanings to each of the arguments
3. refactor KW, from your screenshot it looks like KW is trying to find an item in arguments, why not call KW once per item to get to know which log entry fulfill check statement?

[BeastModeActivated]

Hi
I think there is some misunderstanding.
What my issue is that RED doesn't expand a column as RIDE does.
In our test case, we need to check multiple entities and each entity has many values. So we pass list of dictionaries in each column.
One column represents an entity for us, so we group all values belonging to an entity in one cell and separate them by comma. e.g Opening Date=2016-05-01, Fx Quote Amount=3000.0 etc
Then the next column belongs to a separate entity that will have multiple values too. We need to check all of them.
Keyword "Check Far Leg Allocations" is written such that it will check values for all columns. Each column is in form of a list. So it will parse each column and check values for each.

We follow this concept as it more readable for end-users as they can clearly see what all data is being verified as it is clubbed properly.

Solutions you have mentioned above doesn't serve this purpose I believe.

[KrzysztofJozefowicz]

Ok, now I get it. We will investigate it how to provide wrapping text inside cell when text length is longer than cell width.

[BeastModeActivated]

Thank you.
Any idea if this can be included in next RED release ?

[michalanglart]

Hard to say now, as the team is now occupied with tasks related to test launching (couple of tasks related to #70, which are also needed for internal users and which would open possibilities to launch tests via pabot for example, or may also fix #20 in decent manner).

The change for enabling labels wrapping is probably rather easy, but it would also affect features like hyperlinking in tables (Ctrl + LMB on labels) or matches displaying (when filter is set) plus possible some more.

We'll let you know when we will decide what will be the final content of next release and when it will happen. As for now we plan to do minor release (today, maybe tomorrow) with regression fixes (bug #81).

[BeastModeActivated]

Hi
Can you please share when can we expect this in release ?
It is a lot of trouble for my team to keep switching between RED and RIDE.

[michalanglart]

Hi,

I'm sorry, but we were not able to take a closer look yet.

I will try to implement it tomorrow and see what problems would occur. After that we'll let you know if it would be possible for us to provide it with next release.

[michalanglart]

Hi,

I tried to implement it and it seems to be doable quite quickly, so you can expect to have it implemented with next release.

As to the release itself - maybe within next week; for sure we're planning to make it happen in March.

[BeastModeActivated]

Thank you. Waiting for the release.

[BeastModeActivated]

I just checked 0.7.6 release. Seems this is still not working.
Can you please check whether this has been fixed ?

[michalanglart]

You can configure it in preferences whether cell content should be wrapped or cut like now - by default cut is used as previously.

You have to change it in preferences: Robot Framework -> Editor, then set "When cell is too small for content" to "wrap the content".

[michalanglart]

Side note: changing preference does not change behavior in currently open editors, so they have to be reopened.

Somehow we haven't mentioned this issue in release note, we'll fix that.

[BeastModeActivated]

Thank you