Rapid Prototype Blog

Posts Tagged ‘test’

Overview

All design changes you make to your network must be tested with a proof of concept plan. It is important to test the current design, configuration and IOS versions in a non-production environment or on the production network with limited disruption. Implementation of newer network modules at a router, for instance, could require that you change the current IOS version that is implemented. Making those changes could affect WAN or campus modules already installed at production routers. That is the real value of doing a proof of concept and certifying that the new equipment and IOS versions integrate with each device as well as the network.

Advantages

The following list describes the advantages of doing a proof of concept with your network design.  The proof of concept test results should be examined and used to modify current infrastructure, security and management specifications before generating a design proposal. The proof of concept model suggested here involves prototype design, equipment provisioning, defining tests, building equipment scripts and examining test results.  

The following list describes specific advantages associated with proof of concept testing

•  Address any design concerns without affecting your production network

•  Build and test configuration scripts before implementation

•  Test new IOS, Cat OS and WAN OS versions and firmware

•  Sell design feasibility to the client

Proof of Concept Model

The following numbered list describes all proof of concept components and specific sequence.

1. Prototype Design

2. Provision Equipment

3. Define Tests

4. Build Equipment Scripts

5. Review Test Results

Prototype Design

The prototype is a model for testing design and configuration features in a non-production setting such as a lab. You concern could be with specific protocols or IOS services and how they work with current protocols and IOS services running on your production network. The design should specify topology, equipment, addressing and software versions.

Provision Equipment

Obtain the circuits, cables, devices and servers required for testing. The equipment and software should be identical to the proposed design for specific testing and verification. Connect the equipment as specified with the prototype and make note of specific software versions and firmware being tested.

Define Tests

The tests should be designed to verify the design works as described at all Layers of the OSI model. That would focus on physical, network and application connectivity. The following is a suggested list that should be modified for your particular concerns. Depending on the current network and your tests, it could be an option to implement testing at some access offices with minimal impact on the production network.

The following is a list of typical tests that should be conducted

•  Ping Equipment and Servers

•  Routing and Switching

•  Security Testing

•  Availability Testing

•  Application Load Testing

Build Equipment Scripts

Work with vendors to build the correct scripts for each device. This is particularly relevant if the design will utilize newer equipment and protocols that have yet to be standardized with the industry. Discuss any problems or concerns the vendor has with your current design and, if necessary, modify scripts and design specifics   Review Test Results

The proof of concept test results should discuss specific issues with all defined tests. Note what problems were resolved and those that were referred to a vendor. The test results should be utilized to make changes to the current infrastructure, security and management specifications developed so far before moving on to the design proposal.

Shaun Hummel is author of Network Planning and Design Guide available at amazon.com and CiscoDesignBooks.com featuring Networking Books, eBooks, Certifications, Articles and Design Tools.

Lexi and Lily present their prototype design idea for the School of the Future. Their design has a living roof, solar panels, and a glass floor with a river flowing underneath. The teachers supervise do it yourself learning.
Video Rating: 0 / 5

More Prototype Design Lab Articles

With its dynamic scalablity, flexibility and virtualized resources are provided as a service, Cloud Computing is seen as the dawn of a new era for application services and has received its fair share of plaudits.  With Google Documents, Flickr, Buzzword and Zoho as examples of general purpose applications that use Cloud Computing Technology it is only a matter of time before Cloud Computing is seen as the most viable option for application development and deployment.

With IT Giants such as Microsoft, Google and Amazon all vying for a position within the Cloud Computing space you’d expect there to be a plethora of Cloud based Software Applications  currently available.  Even though this is sure to be the case in the near future, at present Software Testing appears to be the current favoured use of Cloud environments.

A recent survey by Evans Data, an independent research firm that conducts periodic surveys of developers , found that of those using cloud facilities to run applications, 49.8% said they were doing so experimentally or for prototyping; 28.6% for non-critical business applications and 21.6% for business critical applications.  They see Cloud environments as being “good for testing because they can be set and torn down quickly, sometimes at less expense than on-premise facilities”. 

The question to answer then is what Software testing tools are available to aid developers and Quality Assurance individuals in their application development and testing procedures.  Software Testing tools that are used for testing of conventional applications are of little use when applied to Cloud Testing as there is a need for tools to allow Software developers and Tester to analyse the network, desktop and implications of changes within the Cloud.

A growing variety of Cloud based Open Source Software Testing Tools are being published.

Cloud Tools for example is a set of tools for deploying, managing and testing Java EE applications on Amazon’s Elastic Computing Cloud (EC2). Containing three main parts, which includes machine images that can be configured to run on Tomcat and Maven & Grails plug-in this is an amazing tool to use for Open source cloud software testing.

PushToTest TestMaker is a distributed test environment that can run tests on test equipment, or in a Cloud Computing environment.  It introducing specific commands to support automatic Cloud Testing services.

Cloud Tools and PushToTest Test Maker represent examples of products that will help shape the future of robust Cloud based Software Testing Applications.  Though the technology is in its infancy, a number of testing tools are emerging that can provide assistance in cloud based software testing.

Visit Tester Tools for Open Source Software Testing Tools and scripts including a dedicated Cloud Computing Testing Tools section that showcases the latest Cloud Computing Software Testing  tools. If you want to try Cloud Computing Test tools for free Visit http://www.testertools.com

Tester Tools Site: http://www.testertools.com
Follow me on Twitter: @Testertools

Related Software Prototyping Tools Articles

Those that already create a prototype before investing too much time in any problem already know: there are several blind spots and mistakes designers do unwillingly. And those can be avoided by testing and validating the wireframe through several phases, from drawing to high fidelity prototype.

Most of those are common, but some can be really difficult to detect without a test:

Users getting lost while navigating

You know all the content of your site. So, you’ll never get lost, and you always know where you are. You know the site by heart, since it was a wireframe. But should this section really be where you think it is? Leaving hints like breadcrumbs or having colours for different sections is important, but also is testing content categorization.

Blindspots

You think everyone will look at your red-and-yellow banner at the centre of the screen, don’t you? Sorry, they won’t. And it may also happen with other objects. Sometimes, designers and clients become so obsessed with a colour or a photograph that they’re sure everyone will pay attention, but due to several different factors, it doesn’t happen. Testing can uncover some of them.

Standards exist for a reason

It may happen that you have a great idea for a different navigation model, direction or structure. It may be a breakthrough, but also can be a big flop. There’s a reason because most sites today have two or three columns, the main one is bigger, and a big header with navigation on top: it’s become a standard, and everyone is used to look for them there. If you need to create something different, it can be great. But, please, test it until you’re sure users won’t get confused and leave your site empty.

What to do if I find a problem?

If you’re using Justinmind Prototyper, add a comment, and the Ux designers and product managers will know there are some mistakes. Correct them. Adjust. Test again. Rinse and repeat. It always works.

Keep it easy – overexplain if needed

Remember that not everyone come to your website from the homepage. With the increase of Google’s visitors, the number is always bigger. So, it’s important to explain to them what your site is about, and what to do when they get there.

Help your users. Think of them as a foreigner in your country. Although they want to be kind and start a conversation, you created the place, you know the rules and you must teach them (in a kind way, no one wants to be bossed around) how to behave in your website.

A quick test print of the new 3D printer at work

First test with plaster and ink. This shows the print and recharge cycles. layer thickness is 0.1mm ( .003937 inch) I need to make some adjustments to belt tension and improve layer smoothness.

Test print on Z-corp 450 3D printer. The print was a test of facade pattern and scale for a project under development. More information at www.variousarchitects.no

Before any software or website project, it’s vital to test and verify if what’s done is exactly what was initially designed. Practice says that is better to prevent than to fix, so many UX designers nowadays are developing techniques to test and prevent errors using wireframes and prototypes.

One of the main uses for hi-fi simulations is usability testing. With a prototype, you can test all user interactions, gather data and then have the modifications and comments to your clients and all team involved in the project. For this, you need to have a hi-fi wireframe made with Justinmind Prototyper and record users’ reactions, comments and notes.

Several UX designers use complete prototype to simulate a website or software experience, and even with the use of real data to make it work just like it was a programmed piece of software. This saves time and teamwork, and may also improve coding quality, since it generates a better documented process.

Why should you test your functional wireframes

Dana Chisnell has a great article about when you should record usability sessions. It involves what you will and may do with testing, which kinds of results you should expect and even legal issues. It’s a great material.

Sometimes you have a very clear opinion about your idea, but the final users don’t understand. It may seem obvious for those involved in the project, but not for everyone. And they are the ones who will use and buy what you’re working in. So, testing may help you prevent mistakes and huge errors.

But what if your testing shows you’ve got to change a lot of things? Imagine the countless hours of work lost? And the other ones you’ll need to put into the project? This can be avoided using functional wireframes.

How should you do usability tests

To test a functional mockup, you need to follow several steps. It’s not hard, and it’s a much documented procedure. There’s a great article from Microsoft that explains how to define tasks, how many people you need, how to facilitate, moderate and record. (http://msdn.microsoft.com/en-us/magazine/dd920305.aspx)

Usability testing is very important, and we believe Justinmind Prototyper can be a great help to everyone involved in the activity.

Tools for testing: what you should use

There are plenty of options for recording screen, mouse track and users’ faces with a camera. Some solutions were listed in one of our blog posts for recording screen and mouse movements. You can use some camera recording software like Silverback (mac only) for record faces and audio. Then, you’ll have plenty of data to analyse.

The folks at Boxes and Arrows wrote a great review of software necessary to record and track usability testing.

If you want more information about high fidelity wireframes and website prototyping, subscribe to Justinmind’s blog feed or drop us a line on twitter.

After finishing your project and presenting to the client, sometimes it’s needed to do usability tests with a prototype, to understand real users’ needs. So, you can export your hi-fi wireframe into HTML, or even test it remotely using Justinmind Server.

Before doing the test, is recommendable that you:

Prepare the test questions

If it’s an eCommerce site, you’ll need the users to buy something. Maybe have them fill a form and submit it correctly. Ask them questions about information on the site: ex: “how much does the book Hamlet costs?” or “does this site ships to England?”.

Note that these tasks should be the ones users will do more frequently, and pay attention to their mistakes or if they don’t understand something. If it happens to them, may happen to other users.

Do not include hints, or help them complete the tasks. It’s important to understand what users feel difficult to do.

Start with the easier tasks. It helps them improve confidence, and sometimes users get nervous when they cannot complete the first task. Reassure them that there’s nothing wrong if they make mistakes. It’s their job to find the potential mistakes, anyways.

Remember always that when a user fails a usability test, it’s a win situation: you can correct something that can be very harmful and dangerous: investing time and money in a bad usability website.

Finding users for a usability test

It’s important to find potential users to your site. Do not test your social network for old ladies with your graphic design friends. They use computers and have different tastes, goals and approaches to a website.

It’s not needed to test with more than 5 people, according to some researchers. Most of the conclusions with more people are repetitive and come to the same results, so 5 is considered the magic number.

During the test of your wireframe

There’s no need to help the users. If the user cannot complete the task alone, it’s ok. Note that down, and reassure him that there’s no problem. Everything users do may be important, from what they do to what they say during the test. Note that down. After the test, ask users why they’ve done something you didn’t understand.

After the test

Tell them it’s important to understand the tasks they couldn’t do, and then improve the site. Explain them how it was designed to work, because you can find more conclusions there. They must know their feedback is important.

Get all the conclusions and write a report of changes that should be done to the prototype, and, if possible, test again.