Crowdtesting uses crowdsourcing to source testing of software applications and systems. It taps into a global community for testing, helping contain costs and empower users while enabling faster time to market. Conditions for effective crowdtesting include establishing a diverse crowd of experts, novices, and potential users, and controlling the testing environment and portions of software being tested. Augmented Reality (AR) combines real-world video with computer-generated graphics in real-time using sensors and software. Testing AR requires checking functionality of integrated hardware and software components as well as performing task-based testing of the overall system.

1. Ewald Roodenrijs Testing the Future of Testing

2. Remarkable things

4. What are the benefits of crowdtesting?

7. Developing

8. Testing

10. New phenomenon

11. Substitute to traditional testing

12. Focus on acceptance

13. Inspiration from Open Source movementThe use of an unknown crowd of people and knowledge when testing software applications or systems

15. Crowdtesting can complement in-house resources at a practical, tactical level

16. Crowdtesting enables to tap into the creativity and diversity of a global community of skilled professionalsCrowdtesting

17. Key benefits for the customer Cost containment Empowering the user Dealing with Increased complexity Keeping your customers Faster time to market Meeting expectations

19. Novice

20. Specialists

22. Questionnaire

23. The crowdNational security system High Low Control Mortagecalculation 3rd party update Webshop Game Usability check Open Confidential Classified Sensitivity

24. Conclusion

26. What are the benefits of crowdtesting?

29. Examples of Augmented Reality

30. Product enrichment

31. Travel

32. E-learning

34. Fiduciary markers or GPS/compass

35. Image registration

36. Structure from motion

37. Video trackingin real time

39. Microphone

40. Mobile phone (optional)

41. Glasses

42. Contact lensesCustom made software Software Standard software Standard components Hardware

44. Reliability

45. Flexibility

46. Security

47. Usability

48. TestabilityFunctional testing the integrated components because of the highest risk of failure. Custom made software Software Standard software Standard components Hardware

50. User interface check

51. Import/export

52. Help

53. Reports

54. Functional

55. error handlingFunctional example: Is it possible to turn car 180o? Function 3 Standard components Function 5 Function 7 Hardware

56. Conclusion