Thursday, 1 December 2016
Assignment 2: Me Myself and I Testing
For Testing, I tested my website with various types of testing including:
FUNCTIONALITY TESTING
FORMS TESTING
DATA VERIFICATION
AND VALIDATION TESTING
- Functional Testing
- Functional Testing is a testing technique that is used to test the features and functionalities of a website
- Data Verification and Validation Testing
- Data verification is the process of checking that the software meets the specification required
- Validation testing is the process of checking whether the specification captures the potential target audiences needs
- Application Specific Functional Requirements
- Application Specific Function Requirements testing is described as when a user inputs information to the website, how the input behaves and it's output to the user
- Interface and Error handling testing
- Error handing is described as the process of responding to the occurrence, during computation and the exceptions that it may have
- Compatibility testing
- Is the testing of the website to ensure that various browsers and platforms can run the website without any problems
- User Interface usability testing
- Is the process of ensuring the website meets it requirements and can live up to the standards for the user
- Usability testing
- Is when a user is given a list of tasks to perform on a website. This is to ensure that a website meets the highest standards and that the likes of navigation are tested. It is good practice to get a user of the website to do this as they will be able to confirm that they can make their way around the website without any problems, loading time is fast and overall the website is presented in a practical manner.
.
FUNCTIONALITY TESTING
Check
that the link takes you to the page it said it would.
|
✓
|
Ensure
to have no orphan pages (a page that has no links to it)
|
✓
|
Are
all referenced web sites or email addresses hyperlinked?
|
✓
|
If
we have removed some of the pages from our own site, set up a custom 404 page
that redirects your visitors to your home page (or a search page) when the
user try to access a page that no longer exists.
|
✓
|
Check
all mailto links and whether it reaches properly
|
✓
|
Acceptance
of invalid input
|
✓
|
Optional
versus mandatory fields
|
✓
|
Input
longer than field allows
|
Full name may be entered into Name so
field has large spacing
|
Radio
buttons
|
✓
|
Default
values on page load/reload(Also terms and conditions should be disabled)
|
✓
|
Are
all of the parts of a table or form present? Correctly laid out? Can you
confirm that selected texts are in the “right place?
|
✓
|
Does
a scrollbar appear if required?
|
✓
|
Is
the Privacy Policy clearly defined and available for user access?
|
X
|
At
no point of time the system should behave awkwardly when an invalid data is
fed
|
✓
|
Check
to see what happens if a user deletes cookies while in site
|
Default Values are deleted
|
Check
to see what happens if a user deletes cookies after visiting a site
|
Default Values are deleted
|
APPLICATION
SPECIFIC FUNCTIONAL REQUIREMENTS
DATA
INTEGRATION
DATE
FIELD CHECKS
NUMERIC
FIELDS
Check
the maximum field lengths to ensure that there are no truncated characters?
|
✓
|
If
numeric fields accept negative values can these be stored correctly on the
database and does it make sense for the field to accept negative numbers?
|
X Field accepts negative numbers. This
does not make sense for users to insert negative numbers for a contact number
|
Assure
that leap years are validated correctly & do not cause
errors/miscalculations
|
Not Applicable
|
Assure
that Feb. 28, 29, 30 are validated correctly & do not cause errors
|
Not Applicable
|
Is
copyright for all the sites includes Yahoo co-branded sites are updated
|
Not Applicable
|
Assure
that lowest and highest values are handled correctly
|
Not Applicable
|
Assure that lowest and highest values are
handled correctly.
|
Not Applicable
|
Assure that numeric fields with a blank
in position 1 are processed or reported as an error
|
Not Applicable
|
Assure that both + and - values are
correctly processed. Assure that division by zero does not occur.
|
Not Applicable
|
Include value zero in all calculations
|
Not Applicable
|
INTERFACE
AND ERROR HANDLING
SERVER
INTERFACE
EXTERNAL
INTERFACE
INTERNAL
INTERFACE
COMPATIBILITY
BROWSERS
PRINTERS
CONTENT
USABILITY
Verify
that communication is done correctly, web server-application server,
application server-database server and vice versa.
|
✓
|
Compatibility
of server software, hardware, network connections
|
✓
|
Have
all supported browsers been tested?
|
✓
|
Have
all error conditions related to external interfaces been tested when external
application is unavailable or server inaccessible
|
✓
|
If
the site uses plug-ins, can the site still be used without them?
|
X Map must have a plug in
|
Can
users use copy/paste functionality? Does it allows in password/CVV/credit
card no field?
|
Users can copy information. Credit card
and password field is not applicable
|
Are
you able to submit unencrypted form data?
|
Not Applicable. No passwords on website
|
BROWSERS
Is
the HTML version being used compatible with appropriate browser versions?
|
✓
|
Do
images display correctly with browsers under test?
|
✓
|
Verify
the fonts are usable on any of the browsers
|
✓
|
Is
Java Code/Scripts usable by the browsers under test?
|
✓
|
Have
you tested Animated GIFs across browsers?
|
Not applicable
|
VIDEO SETTINGS
Screen
resolution (check that text and graphic alignment still work, font are
readable etc.) like 1024 by 768, 600x800, 640 x 480 pixels etc
|
Not applicable
|
Colour
depth (256, 16-bit, 32-bit)
|
Not applicable
|
CONNECTION SPEED
Does
the site load quickly enough in the viewer’s browser within 8 Seconds?
|
✓
|
Text
and image alignment
|
✓
|
Colours
of text, foreground and background
|
✓ Consistent
|
Scalability
to fit paper size
|
✓
|
Tables
and borders
|
✓ Consistent
|
Do
pages print legibly without cutting off text?
|
✓
|
User Interface Testing Checklist
COLORS
Are
hyperlink colors standard?
|
✓
|
Are
the field backgrounds the correct color?
|
✓
|
Are
the field prompts the correct color?
|
✓
|
Are
the screen and field colors adjusted correctly for non-editable mode?
|
✓
|
Does
the site use (approximately) standard link colors?
|
✓
|
Are
all the buttons are in standard format and size?
|
✓
|
Is
the general screen background the correct color?
|
✓
|
Is
the page background (color) distraction free?
|
✓
|
All
fonts to be the same
|
✓
|
Are
all the screen prompts specified in the correct screen font?
|
✓
|
Does
content remain if you need to go back to a previous page, or if you move
forward to another new page?
|
✓
|
Is
all text properly aligned?
|
✓
|
Is
the text in all fields specified in the correct screen font?
|
✓
|
Is
all the heading are left aligned
|
✓
|
Does
the first letter of the second word appear in lowercase?
|
✓
|
IMAGES
Are
all graphics properly aligned?
|
X
One image on lowcost products is not properly align
|
Are
graphics being used the most efficient use of file size?
|
✓
|
Are
graphics optimized for quick downloads
|
✓
|
Assure
that command buttons are all of similar size and shape, and same font &
font size
|
✓
|
Banner
style & size & display exact same as existing windows
|
✓ Except for the use of font
face on facecare page
|
Does
text wrap properly around pictures/graphics?
|
✓
|
Is
it visually consistent even without graphics?
|
✓
|
INSTRUCTIONS
Is
all the error message text spelt correctly on this screen?
|
X
no error messages
|
Is
all the micro-help text(i.e. tool tip) spelt correctly on this screen?
|
✓
|
Micro
help text(i.e. tool tip) for every enabled field & button
|
X
|
Progress
messages on load of tabbed (active screens) screens
|
X
|
NAVIGATION
Can
all screens accessible via buttons on this screen be accessed correctly?
|
✓
|
Does
a scrollbar appear if required
|
✓
|
Is
there a link to home on every single page?
|
✓
|
When
an error message occurs does the focus return to the field in error when the
user cancels it?
|
No
Error Messages
|
Are
all the field prompts spelt correctly?
|
✓
|
Are
fonts too large or too small to read?
|
✓
|
Are
names in command button & option box names are not abbreviations
|
✓
|
Can
the typical user run the system without frustration?
|
✓
|
Do
pages print legibly without cutting off text?
|
✓
|
Does
the site convey a clear sense of its intended audience?
|
✓
|
Does
the site have a consistent, clearly recognizable “look-&-feel”?
|
✓
|
Does
the site look good on 640 x 480, 600x800 etc.?
|
✓
|
Is
all terminology understandable for all of the site’s intended users?
|
✓
|
Overall, I believe testing of my website really well. It enabled me to see what I could do to my future websites but also enabled me to ensure the website is suitable for the target audience.
Assignment 2: Me, Myself and I Deployment Update
Upon research, I was finally able to get the map working with an API. To do this I followed these various steps:
- Go to the Google API Console
- Create a new project
- Click continue to enable the API
- On the Credentials page, get an API Key
Once I retrieved my key I got my co-ordinates online to specify my location. I inserted my API key to my map and commit the changes through terminal. These changes worked.
Subscribe to:
Comments (Atom)