[keynote] Enjoy the Ride! by Henrik Roonemaa
Very good talk for the keynote: interesting, not very technical and a little bit off topic. Some short takeaways:
- There are two types of bad products: those that exit the market and those that enters it.
- iPad has a great intuitive design – that's why it's the future. Not for technical people, but for the majority.
- In the internet you are for everybody or for nobody.
- The product should do something for me, not me doing something using the product.
[workshop] How to Build a Robust API Checking Framework by Mark Winteringham
[workshop] Me, Myself and Siri by Sami Söderblom
- @seeBotsChat – Twitter account of two AI robots speaking to each other
- Quick Drawing – game-ish neural network, that recognizes human's doodling
- Perpective – API that tells you how many people will be abused by your text etc
- Wolfram Alpha – API that measures and compares everything
[keynote] Creating Yourself as a Tester – make your own testing path by Alan Richardson
- Describe rather than define.
- Do notes about how you work and analyse them later to work better.
- People who came up with software testing knew math and physics very well and they generalized some complex stuff to known testing methods. But to understand the roots of these methods you could learn math and physics as well.
- People are complex systems. If you are trying to copy someone you are coping only high level of the whole system. That's why you need to develop your own system with roots and low levels.
[keynote] 10 Commandments for Ethical Software Testers by Fiona Charles
- Developers don't even know that libraries, that they are using, collect users data.
- Big data is fed into fare and independent algorithm, but this data was selected by someone. Data is biased.
- There are risks in acting, there are risks in not acting. How much risk do you tolerate?
- If you have concerns – make good solid notes for future evidence.
- We develop systems, because we can. Not always because it makes the world a better place.
[talk] Test Your Java Applications with Spock by Iván López
[talk] A Story of a Tester Building his First Mobile App by Risko Ruus
[talk] Determining Your Application's Heartbeat Through Monitoring and Logging by Gwen Diagram
[keynote] Building Smart and Reliable Self-Driving Robots by Kristjan Korjus
- They limit speed of the robot to 6 km/h, so it won't be classified as self-driving car and won't fall into regulations.
- Software can help to get maximum out of a crappy hardware.
- They don't have tests and documentation, because hardware is changing too quickly.
- To avoid security issues related to 9 cameras on robots, no person ever see pictures with normal resolution, so it's impossible to see numbers or faces.
- Craziest people are in London, who says something like that's my street, I don't allow robots here!
- There is no self-destruction system, because they don't have tests and what if there is a bug in this system? :)
Notebooks with conference floorplan and tracks description is cool, as always.
Drum show with drum sticks is the best!