autoclose feature for tests?

[Andi-K]

I think we need to implement inside show_gui() something like
I'll implement this:

if env::var("KISSUI_AUTOCLOSE") {
   init_fn().add_child(
       Timer::new()
       .set_interval(10000)
       .set_on_interval(|_ : Timer|{CallbackStatus::Close})
       .start())
} 

The PR is coming soon, just need to impl add_child().

@cybergeek94

If you have any ideas for some unit tests that we can add without needing a GUI to actually launch (since Travis-CI workers are headless), let me know. I'd like to be able to catch as many logic errors as we can with cargo test.

I didn't really dealt with cargo test and Travis-CI yet.
Testing a GUI without using it sounds hard to do.
But i see Travis-CI can run Firefox and may IUP/GTK too.
Then we can use kiss_ui::timer::Timer to autoclose the GUI and test everything we want.
Or do i miss something?

Furthermore we can use ImageMagick and write a script for a advanced test:

• set the environment variable KISSUI_AUTOCLOSE
• loop through the examples
  • cargo run --example x
  • make a screenshot import -window
  • compare it with the screenshot on github
  • report if the screenshots aren't equal or cargo's exits status is not 0

If we can't run this script on Travis-CI we just keep in mind that different environments produce different screenshots.

[abonander]

Well I was mainly thinking of testing different logical stuff, like the string borrowing code. Unit testing isn't about checking out the whole program at once; that would be integration tests. Unit tests are supposed to be short sanity checks that make sure that a change in one part of the program didn't break it somewhere else.

Of course, there's nothing stopping us from doing integration tests as well. There's probably at least one framework for writing scripts to test GTK+ applications at a high level, so you can script up button presses and keystrokes and ensure that the application responds correctly.

[Andi-K]

I know you didn't want test the whole example at once. But hey why not? You don't need to run it for each commit.
And to test the string borrowing code you need at least one WidgetStr and for it a Widget, but Winget::new() is "invalid KISS-UI context" outside show_gui(). Right?
So you have to test it this way or don't use .show() inside show_gui() while running tests.