Blog post for gtk-test release #73
Conversation
|
@GuillaumeGomez Thanks, now we have way to test gtk in .travis too. |
|
|
||
| Hi everyone! | ||
|
|
||
| Today is not about a new [`gtk-rs`] release but about a new crate being released. Let me introduced to you: [`gtk-test`]! |
|
|
||
| Today is not about a new [`gtk-rs`] release but about a new crate being released. Let me introduced to you: [`gtk-test`]! | ||
|
|
||
| So what's the purpose of this new crate? Simply to test UI. Currently, testing UIs is difficult, but with [`gtk-test`], you can check basically everything UI-related way more simply. |
There was a problem hiding this comment.
Simply to test UI -> UIs
way more simply -> simple
check -> test?
There was a problem hiding this comment.
Doesn't make sense with "simple". :-/ Or did I misunderstood what you meant?
There was a problem hiding this comment.
Simply to test UIs. Currently, testing UIs is difficult, but with [gtk-test] you can test basically everything UI-related way more simple.
But better ask a native English speaker if unsure :)
|
|
||
| So what's the purpose of this new crate? Simply to test UI. Currently, testing UIs is difficult, but with [`gtk-test`], you can check basically everything UI-related way more simply. | ||
|
|
||
| Now you might wonder: how does it work? We send UI events to the window. So if your window isn't on top of all other windows, events won't work (not on your window at least). This is an issue on OSX for example (there is a workaround luckily). |
There was a problem hiding this comment.
That OSX issue seems like something for a footnote, not in the middle of the text :) And with a link to the relevant bug report in Bugzilla and PR
Also maybe mention that windows can be brought to the front by GTK
There was a problem hiding this comment.
No, the issue is that you can't bring the window to the front on OSX. But I'll remove the part about osx issue.
| } | ||
| ``` | ||
|
|
||
| Tadam! The newly created `observer` will look and ensure that the given signal has indeed been called (if not, it'll obviously get stuck at `observer.wait()`). |
There was a problem hiding this comment.
Does this have a (high) timeout, like 20-30s or so, or an optional timeout when it fails? That would seem useful to prevent CI from hanging forever and let the test cleanly fail and proceed to the next test
There was a problem hiding this comment.
No it doesn't. However, if you're using cargo test, the timeout is 60 seconds.
cc @EPashkin @sdroege @antoyo