% Lokální makra patří do hlavního souboru, ne sem.
% Tady je mám výjimečně proto, že chci nechat hlavní soubor bez maker,
% která jsou jen pro tento dokument. Uživatelé si pravděpodobně budou
% hlavní soubor kopírovat do svého dokumentu.

\def\ctustyle{{\tenss CTUstyle}}
\def\ttb{\tt\char`\\} % pro tisk kontrolních sekvencí v tabulkách

\label[Testing]
\chap{Testing}

As the main part of testing, I've chosen user testing, as the application has a very high focus on being user-centric. 

The front-end part of the application would be tested, with not all features that where mentioned during the design are implemented in the final form as I wanted to make sure that they would bring value to the user and it would be figured out through this testing. But the core features of the application are working and you could use the application.

Each user testing would be split into three parts. The first is a pre-test set of questions focused on experience with the problem and similar applications. The second part is the testing of the application itself. I haven't set any goals for the user I've just let the user use it and let him tell me anything that is missing in his opinion or something that doesn't make sense. The last part would be a post-test set of questions that are focused on the application itself if they think it brings any value to them.

I had five users with various experience with the platform from the targeted audience test the application, and I will summarize the test for each one of them.

\label [Participant 1]
\sec Participant 1
This user has no prior experience with this kind of testing and has limited experience with iOS platform. The user visits the cinema once a month on average and already tried different ways of displaying screenings on a smartphone but found it no optimal with problems with displaying the information on a small screen.

During the testing, the participant had a few things to point out on the design. He missed the feature to search on screens with a list, to limit the number of displayed information. Also, the participant would like to see the films that are coming soon. 

The user felt that the application is intuitive and didn't any need any assistance with navigating through the application. But he would like to have an option to reserve or buy tickets through the application and to see more information about the screening itself.

\label [Participant 2]
\sec Participant 2

This participant had already tested application in this form and has no user experience with iOS platform. The user visits the cinema once every three months on average. The participant has experience with searching for screenings on a smartphone and found that the limiting factor is the lack of optimization for smaller screens.

The participant pointed out few missing features during testing. The main missing feature was the lack of search functionality. The other thing was a missing option to have the next step on the display of screenings to reserve the ticket. The last thing the participant pointed out is the lack of details for screenings.

The participant didn't run into any navigation issues, and he always knew the next step in the application and that it felt intuitive. He only missed the detailed information about screenings in that meaning if it has subtitles and if it's for instance in 3D and the option to be redirected to the reservation.

\label [Participant 3]
\sec Participant 3

This participant also has prior experience with user testing and uses iOS-powered devices on a daily basis. This participant goes to the cinema four times a month on average and has only experience with searching screenings using the web browser on a mobile device but states he misses optimization for smaller screen devices.

During testing of the application, the participant pointed out that the application is missing date separation in the screenings list and the ability to search for specific films or cinemas. The participant also suggested displaying the screenings in a scrolling table so you would have everything even easier to navigate.

The participant didn't face any issues with navigation through the application and felt intuitive. He didn't state any lack of information that the application offers to him. He also stated that he feels that it's a better option from that are available.

\label [Participant 4]
\sec Participant 4

This participant has never attended in user testing of any application. He has experience with searching for screenings only using the browser and navigating through websites for cinemas. The problem in this is the lack of optimization for smaller screens devices with a touchscreen interface in his opinion.

During the testing, the participant pointed out few problems he faced or things he missed in the application. The first was the lack of date corresponding with screenings so you would know that time but not the date. The next thing from screenings screen he missed a way to reserve the ticket. The participant also point out few things like localization to an American way of displaying time and a missing title on a screen.

The participant didn't face any navigation issues during the testing and felt the application was self-explanatory and simple. He stated that he would like to have an option to reserve tickets and have more information about the cinema. In the end, he stated that he feels that this application is a better option than the market already has.

\label [Participant 5]
\sec Participant 5

This participant was never part of user testing of an application and also has no experience with the iOS platform. The participant goes to the cinema twice a month on average and has no experience with searching for screenings other than the website on the smartphone. Which by his words is not optimal and unoptimized of touchscreen devices.

During the test, the participant didn't run into any major issues. The participant was missing some features like clicking on screening date to reserve a ticket and on the same screen missed separation into days. Another thing was lack of search functionality and suggested to add more information to the film detail screen.

The participant stated that the application felt intuitive and didn't face any problems navigating through the application. The participant also stated that this is a better option than other currently available that he had experience with.

\label [Conclusion]
\sec Conclusion

As a disclaimer, I would like to state again that the testers didn't test a feature full application but a prototype with core functionality in place. This way we know early on in the development about core problems of the idea behind the application. Also, this gives us the information about next features to priorities.

In conclusion, the participant seems to like the idea, the design and how is information provided. There were common issues across all participant. For instance the lack of search functionality, that is part of the design but was not part of the testing version. This as would make the application a lot more flexible. 

The other common problems were issues that were not accounted for in the design itself. But can be easily fixed. For instance the lack of date in the screenings list. 

The last major issue all participants faced were the missing option to be redirected to reserve a ticket. This feature would need a change of design because on tap had a different purpose.