100%(15)15 out of 15 people found this document helpful
This preview shows page 13 - 16 out of 28 pages.
Drawing Simulation takes long to load"A large number of tickets was entered. This will take a few minutes."Wait for the application to load the numbers and display the next page or close and re-open the application.13
Lottery Number Generator Final Report| Group 3 Test Plan and ResultsThe test plan and results will be to assist in detailing the approaches taken in testing the Lottery Number Generator Application (LNGA). The test plan will verify that the application is developed in accordance with established standards for software testing. The lottery number application will allow a user to:1) manually enter lottery numbers between a certain range, 2) automatically generate numbers with the click of a button. Both features will be tested to ensure that the user can use the application smoothly with no bugs. There will be no limit on the number of users who visit and pick random numbers at a time for the application. From this point, it will also be vital to test that the randomization algorithms are correctly working and users are not receiving duplicate numbers. Test ItemsThe listed requirements and components detailed in the Project Summary area of the Project plan will be tested. Ensuring data input and output testing is just one area to be tested. The interaction between the user and how the interface responds is a related test item. It is also important that the interface for the user is clear and inviting to beginners and not complicated. Ensuring the buttons on the GUI work as intended albeit basic, will be an integral part of the process as well. Features to be Tested/Not TestedThe above listed features of the application, manual input of random numbers, the automatic generation button as well as the overall interface and user interaction will be tested. 14
Lottery Number Generator Final Report| Group 3 With the pace of the project, it will be the goal to make as a secure application as possible but a full-blown test of the security of the application is not feasible. ApproachIn accordance with established standards, testing will be done by the Design lead which is referred here as “Smoke Testing”. The Design lead and the rest of the team if needed, will conduct a basic overview of the code and ensure that most importantly the code runs properly without any errors. The group effort to review the code will allow the members to get eyes on the application and provide feedback whether positive or negative. Once the team is comfortable with the basic level of the design, the next step will be to ensure that the application is working as intended, buttons, interface, etc. Testing can be automated with the help of projects like “Codacy”, an analysis software, NetBeans JavaHints or manually by the designer, Testing Lead, and group members.