Developing and Testing - projectblog3.files.wordpress.com€¦ · Web viewUnit title – 14 Event Driven Programming. Assignment title ... Introduction. This report will ... Evidence

Developing and Testing

Assignment 3

Damian Kopacki

Name of course – BTEC Level 3 Extended Diploma in IT (Software Development)Unit title – 14 Event Driven ProgrammingAssignment title – Assignment 3

IntroductionThis report will show evidence for testing in two sections, the first is a white box testing strategy where I will show evidence of debugging throughout the development of your application and the error messages you received to highlight errors in your code. The second section will follow a black box testing strategy where I will test the application as a user without looking at the code. For this you will need to create a test plan with at least 10 tests on the template provided detailing the test, what data will be entered, what are the expected results. I will evaluate my application giving examples and evidence for each of the statements you make to help the reader fully understand the points you are making. Include an evaluation against the specification requirements of the application to show if you feel these have been met and how they have been met. Detail the positive and negative aspects of your program then reach a conclusion based on all the evidence and discussion you have provided

Black Box Testing

Test No.

What is being tested How will this be tested

ExpectedResult

ActualResult

ActionTaken

1 Opening the Add page on the staff system

This will be tested by opening staff system program

and then using the mouse clicking on the add button.

The add page will open

Add page open successfully

No action was taken

2 Opening the view page on the staff system


and then using the mouse clicking on the view button.

The view page will open

The view page opened successfully

No action was taken

3 Exiting the system from the menu page on the staff

system


and then using the mouse clicking on the exit button to close the program

down.

The program will close down

The program closed No action was taken

4 Help Buttons on the menu page

Using the mouse to click on the box

with the question mark in it

When the button is clicked a pop up

message will appear with instructions

The pop up message appeared

No action was taken

Name- Damian Kopacki Reg no - 1


5 Help Buttons on the add page

Using the mouse to click on the box

with the question mark in it

When the button is clicked a pop up

message will appear with instructions

The pop up message appeared

No action was taken

6 Save button on the add page Using the mouse to click on the button to save the details inputted into each

field

When the fields are filled out and the save button is clicked then all the

details will be saved to a records

text file

The details where saved into the file and where able to be viewed on the

view page

No action was taken

7 Menu button on the add page

Using a mouse to click on the button

Will return to the menu

Returned to the menu

No action was taken

8 Entering text in the text boxes on the add screen

Using keyboard to input data into

fields

Able to enter text into text box

Text was successfully entered

No action was taken

9 Loading the file in the view page on the staff system

This will be tested by going into the

view page to make sure that the

records file has loaded and there is

text in each field

Once clicked on the view page the

records file will load with all the

fields contain correct text

The program wouldn’t open due

to errors

There was a line of code

missing stopping the

program from opening.

Evidence is in Appendix 1

10 Previous button on the view page

Using the mouse to click on the

previous button

The previous record should

show up

When clicked on the button the previous details showed up in

all the fields

No action was taken

11 next button on the view page

Using the mouse to click on the next

button

The next record should show up

When clicked on the button the next

details showed up in all the fields

No action was taken

12 Menu button on the view page

Using the mouse to click on the menu

button

Should return to the menu

Returned to the menu

No action was taken



Appendix 1Before

The images above show that after the whole program was finished it still couldn’t be opened due to there being an error in the code.



After

The images above demonstrate that there was one code of line missing which is the code highlighted in blue, afterwards it worked successfully when it was added.



White Box Testing1) Before

The images on the left shows that the next button doesn’t work, due to an error within the code. The first image is the code before any changes were made and the bottom image is what happens when u run it with the wrong code.

After

The image on the left is the fxed version of the code. RecordDisplay+ was changed to RecordDisplay++.



The image above shows what the program is when the fixed code is complete. It shows the next button working going from one record to the next.

2) Before

The image above shows the code before it was fixed. The code is for the exit button on the main menu, however it was coded wrong.

After



The images above show the fixed code for the exit button, the problem was that it should have been close() instead of exit().

3) Before

Finally, the images show that the help button doesn’t work because there is an error within the code.

After

The images above demonstrate that the error in the code was that it should have been messagebox::show(“ “) and not message::show(“ "). Furthermore, the top image on the right shows the pop up message working successfully after the code being changed.



EvaluationThe client for Burnley Computer Solutions has asked to create a system that will hold all staff details, due to the company growth throughout four years and they need a clearly define roles and create a more effective system management structure. Their current system isn’t effective in updating the records as it’s paper based and the person in charge of it has complained. The new system needs to have the following information: Staff Name, Address, Postcode, Payroll Number, Job Title, Annual Salary & Tax Code. Also they require that department should be included in the system, the departments will record the department that each member of staff belongs to. Furthermore, the payroll number will be automatically generated by the system using an incremental count of staff added. The system will need to be menu driven with options to add and view staff records and exit the system; in addition the system will need to contain validation which makes the system more secure and durable. On the view details screen the first record will be displayed and there will be buttons available to scroll through the records one by one both forwards and backwards.

The image on the left is the main menu for the staff system program, on the menu there are three options which are “Add”, “View” and “exit”. Furthermore, the menu contains a title to notify the user what the page is and there are help buttons next to each button to instruct the user what to do. The image below demonstrates the pop up message that appears when the help button is activated by clicking it.

The image on the right is that pop-up message that appears when the help button is pressed, the pop-up style is the same for every help button on the system but each help button will have different instructions.



The image on the left is the add page on the staff system program. There are 7 fields to be filled with one being a drop down list which is the requirement set by the client. Furthermore, the page contains a title to notify the user what page it is and it has two buttons, one being the save button which ultimately saves all the information in the fields to a records file. The other button is the menu button which directs the user to the main menu. To get to this add page the user will need to press the add button on the main menu. There are also help button alongside each field and button to instruct the user what to do.

Finally, the last page on the staff system is the view page, this is where the user will view the add information from the records file. On the view page there is an extra field which is the payroll number; this is an automatic number which increases each time a record is added. Yet again to get to this page the user will need to click the view button located on the main menu of the system. This page contains three buttons, which are previous, menu and next. The menu button navigates the user to the menu and the previous button will display the previous records in the records file, if there are no more records that a message will pop up saying there are no more records. When the next button is clicked it will display the next records in the file and if there are no more records a message will pop up. On the view page the user can’t make any changes to the records only view them.

The staff systems design is very professional looking, due to its light plain colours. The buttons are all the same apart from the menu to indicate they are the main buttons. There are titles on every page so that user knows what page they are on and help buttons are provided for the more novice users or beginners to the organisation. The system meets all the requirements the client has asked for which are mentioned in the beginning of the evaluation.

Positive aspectsThe positive aspects of the staff system is that it is very easy to use and no manual guide is needed and if further help is needed then on screen help is provided through the use of help buttons. Furthermore, the user is able to navigate from page to page by the use of buttons; the user can return to the menu from every page and from the menu the other pages. Also the system is user friendly by using large text for anyone with visual difficulties and plain colour for anyone who is colour blind. Finally, the new staff system will be beneficial, due to it will be more effective to the company as it minimises the difficulty of updating the existing records saving a huge amount of time. The online system will be in one place and not all over the place like the paper based system making it more organised. The new system will reduce the chance of mistakes being made, due to validation being put in place.



Negative aspectsHowever, there is room for improvements within the system as more validation could be added to prevent errors from the user side, such as all the fields need to be filled out, format validation for annual salary and tax code and text limit on each field, all of these validations will secure the system from having incorrect data held about a person. Furthermore, once a record has been added it can’t be deleted from the program leading to having a lot of records added by accident meaning the capacity of the system will be larger and there will be more records to view when the user to trying to find a specific record of a staff member. When the user exits the system it doesn’t ask where to save the current data and to make sure the user want to close the program. This is important because if the user fills out the information but doesn’t click save and closes the system by accident the user will lose the staff details.

ConclusionOverall, the staff system has met the basic requirements that the clients has asked for, there is room for improvement to make the system more complex and diverse with validation to ensure no mistakes are made by the user. The overall design of the system looks professional and simple to use.


Developing and Testing - projectblog3.files.wordpress.com€¦ · Web viewUnit title – 14 Event Driven Programming. Assignment title ... Introduction. This report will ... Evidence

Documents