You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Multiline test descriptions not shown completely in test tree #3119
I guess we could replace these with spaces when setting the node label, although you're going to end up with a lot of whitespace in the name here: "bike, than it should". It may be better to use adjacent string literals to split the text over two lines, so there's no actual newline and/or indenting in the actual test name?
(btw, I think there are a few typos of "then" being "than" in there!)
It may be better to use adjacent string literals to split the text over two lines, so there's no actual newline and/or indenting in the actual test name?
I agree, but I think it should still work. Either by making the entry in the test tree multiline, or replacing the line breaks with whitespaces.
Yep, agreed. I don't believe we can have multiline tree nodes (a VS Code limitation), but we can replace the newline. I'll fix that, but I mention it only because I think the spacing will still look weird for the example above, and I don't think it makes sense to try to massage the strings here (beyond the newline replacement).
Activity
DanTup commentedon Feb 4, 2021
I guess we could replace these with spaces when setting the node label, although you're going to end up with a lot of whitespace in the name here:
"bike, than it should". It may be better to use adjacent string literals to split the text over two lines, so there's no actual newline and/or indenting in the actual test name?(btw, I think there are a few typos of
"then"being"than"in there!)HerrNiklasRaab commentedon Feb 4, 2021
I agree, but I think it should still work. Either by making the entry in the test tree multiline, or replacing the line breaks with whitespaces.
DanTup commentedon Feb 4, 2021
Yep, agreed. I don't believe we can have multiline tree nodes (a VS Code limitation), but we can replace the newline. I'll fix that, but I mention it only because I think the spacing will still look weird for the example above, and I don't think it makes sense to try to massage the strings here (beyond the newline replacement).
DanTup commentedon Feb 16, 2021
I ended up tidying the indentation anyway, so they look a little neater.