Development and testing of mobile application for remaining number of patients review in queuing system

U ovome radu izrađena je mobilna aplikacija za pregled preostalog broja pacijenata u redomatskom redu. Aplikacija prikazuje stanje u redovima bolnice koju korisnik može odabrati ili učitati pomoću QR koda. Također, korisnik može unijeti broj s listića iz redomata i tako dobiti informacije o trenutnom stanju za točno taj broj. Aplikacija je napravljena po uzoru na CLEAN arhitekturu i obrazac dizajna MVVM za dijelove korisničkog sučelja. Aplikacija je rađena kroz razvoj programske podrške vođen testiranjem na primjeru pa su tako provedeni testovi jedinica gotovo cijeloga koda aplikacije, a nakon izrade provedeno je testiranje performansi i ručno testiranje prema testnom scenariju. Ako programer nije uvježban i tek započinje s razvojem programske podrške vođenim testiranjem, vrijeme za pisanje aplikacije bit će znatno duže od onoga uobičajenoga. Testovi performansi pokazali su da je aplikacija stabilna i fluidna i da ne postoje curenja memorije niti procesi koji preopterećuju procesor. Kvaliteta aplikacije na kraju je provjerena ručnim testiranjem po predloženom testnom scenariju koje je pokazalo da aplikacija izvršava sve zadane funkcionalnosti bez pogrešaka.In this paper the goal was to create mobile application to view the remaining number of patients in a row. The application displays the status in the hospital rows that the user can select or load using a QR code. Also, the user can enter a number from the list from the ticket dispenser and thus obtain information about the current status for that exact number, the data is continuously retrieved from the server and the constant status in the rows is displayed at all times. The application is modeled on the CLEAN architecture and design form MVVM for parts of the user interface. The application was developed through an approach of test-driven software development, so unit tests of almost the entire application code were performed, and after development, manual testing was preformed according to the test scenario, and performance testing was preformed too. The approach to developing test-driven software has proven to be excellent and the only downside is the time it takes to learn how to apply it properly. If the programmer is not trained and is just starting to develop test-driven software, the time to write an application will be much longer than usual, but once the principle is well learned and practiced, it produces great results and it is definitely worth starting with this method of software development. Performance tests have shown that the application is stable and fluid, there are no memory leaks or processes that overload the processor. The quality of the application was eventually verified by manual testing according to a test scenario, which showed that the application performs all given functionalities without error