Screencast for UI Automation testing

[sohilpandya]

As suggested by @nelsonic and doing some research on YT, there doesn't seem to a UI Automation Tutorial out there, so might be worth getting one up just to see what the response is like.

Todo list for the tutorial

• walk through the current state of the app
• explain a scenario you would like to test
• record that scenario
• write test for that scenario
• run test for the scenario and see it in action.
• talk about caveats (swipe feature, the recording interrupted by error message etc.

[sohilpandya]

• Start the video with a little hello
  • talk about the subject that will be discussed in the screencast
  • What is UI automated testing, it's where tests drive the application through the user interface and see if the result is as expected with the user interface functioning correctly

[sohilpandya]

Here is the outcome of this screencast. https://drive.google.com/a/dwyl.com/file/d/0BzAgO1bmVDtpdUgzMjNGQ1YzMk0/view?usp=sharing

Can you please watch it and let me know what you make of it. I'd like to put it up on our YouTube channel but need an intro segment. 👍

[nelsonic]

"very short tutorial" 12:42 😉
Much of the text is illegible on my tiny screen:

But bare-in-mind that my screen has more pixels than most phones (where many people consume content) ... and if you check the latest stats, the "crapy" 1366 x 768 resolution is still by far the most popular on Laptop & Tablet:
http://gs.statcounter.com/#resolution-ww-monthly-201704-201705

As for the content it's really good. ✅
But, as discussed a "demo" of the test running would be a great intro ...
I would split this tutorial into similar sections to @Cleop's table in: dwyl/tachyons-bootstrap#9 (comment)

Let's be clear, the video is already good and you should publish it
and see if you get some public feedback from the people who attended the Swift meetup.

But if you want to improve it, you could cut it down by a few minutes and improve the organisation.

1. This is automated UI testing in action (15 seconds of demo)
2. We do automated UI testing because it improves the reliability of our apps which means we can ship features faster. (10 seconds show good reviews for app like CityMapper and bad reviews for app that crashes)
3. Here's the "hello world" of UI testing from scratch (3-5 mins)
4. Here's how you add UI testing to an existing app (show dwyl's app for 3-5mins)
5. Conclusion: testing is easy, makes your app better and means you will get paid more as a developer. The End. (1 min)