Development Reviews Testing Upgrade Web Technologies

Many methods, many implementations.

Just like in coding there’s many methods, there’s also many implementations.

From NuGet to NPM, to CDN’s.

A mammoth system using all three can get confusing very quickly.

Let’s start by the most famous framework out there Bootstrap!

Imagine there are different variations of it.

The original, the Sass, the older version (just because it was release with a version name), the third party types (usually plugins that provide additional functionality with their version of compatibility to Bootstrap).

And let’s associate this is within NuGet.

Then bring in NPM an alternative, where front end tech stacks can be searched online and installed through command lines using webpack or something similar to bundle and serve.

Of course you may find Bootstrap in NPM and many variations of it, so be careful.

Then add the CDN, often used to serve code from different servers across the globe for performance boost.

It soon becames apparent there are multiples of frameworks or packages being used.

Then you’ll find them also added in different places, let’s say in different pages.

It really doesn’t get any easier and wondering how it became like this is probably best to ignore and forgive as there could be multiple factors involved.

So the aim is to consolidate the variation to one and keep any plugins used by checking their compatibility.

Where there’s multiple implementation, replace it with one direct access checking it’s version in the process or upgrade it to its latest.

In an ideal world, keeping on top of version control is an advantage.

Developers can stop hacking and develop features faster and for users to gain access earlier.

It was time to address this mess, for our development purpose mostly, but also our users.

Allow me to explain.

In development, developers often find using a framework and looking at new online documentation just because it’s available.

Usually with the less experienced developers you may find them hacking their current version to look or behave the same as to the online documentation.

That’s a no no right there, don’t even go there situation.

Developers should check their current version and find the relavent document version and work from there.

Then there’s the fact of customised features built on top of the framework.

This is the bit that can get complex, if not done the Bootstrap method using it’s classes.

On the other hand for the users, it would be a big performance boost.

Again, allow me to explain.

Refresh rates feeling like a flicker rather than a loading spinner.

But that also depends on the scenarios.

If a user is just loading a page that’s great.

If a user is querying the database it could take some time, depending how complex the search is and how much data is there.

So expect loading spinners there.

If it’s a simple search with very little data to filter from, expect a performance boost.

Apply the users to busy environments and you may find an increment of performance a cross the floor.

Development Testing Upgrade Web Technologies

Fascinating or some what frustrating?

So many courses from different providers.

Which ones are politically correct?

Spending time, involves patience.

As we grow, time feels short.

It’s not always a simple as it looks.

Sure you can follow…

But there are obstacles along the way.

The kind that are not transparent in guidance.

Lessons learned, it will never be.

Acknowledging this…

The cycles of improvement are never-ending.

So the main thing to take from this…

You’re in control, you can’t please all, but you can align the balance with the majority.

Simplify processes not just for yourself, but for everyones case.

With simplicity comes flexible, growth, speed and expansion.

Navigate the play field.

Be your best in the given circumstances.

Die trying, you may get lucky.


Testing procedures for the web

What is Usability Testing?
Usability testing is commonly used to test something new, a product or service, and measure the reactions of audiences to it. Feedback is then used to improve it with the owner, inventor or developer. The same process occurs again until the owner is happy with it.

One may think this process could become repetitive, but fear not! Only test the most important issues that occur the most and are generally higher priority.

What is Accessibility Testing?
This is concerned more with people with disabilities. How would one interact with something if they were blind, deaf or unable to physically touch and move something? These are the major concerns to address and solve. This is similar to usability testing.

Do not mistake Focus Groups as Accessibility & Usability Testing!
Focus groups are groups of people (roughly 5 to 8) working together as a team about ideas and design to gather all thoughts into different concepts.

Usability testing is a one person process guessing which item to test and how to use it.

In contrast, accessibility testing is focused towards disabled people, inventing alternative methods when using products or services.

But focus groups have advantages, they can determine what the audience wants and needs and also test the idea behind the site, making sure it makes sense and it appeals to them.

The disadvantages are that it is difficult to acknowledge whether the product or service works and if improvements can be made.

Focus groups are better done in the research task and during the idea generation and development process for fine-tuning, but don’t mistake them for usability testing. They cannot tell whether people can use the product or service.

So when should test take place?
It’s common sense to continue testing throughout the whole process. When researching, there’s a test to compare existing products or services in competition. After idea generation, ideas can be compared and combined into one final idea. Various problems may occur which can be corrected.

Who should do the testing?
By now, one will know how many tests are to be done, but the first test should be done with a small group of all ages and genders who know about a product or service. After this anybody will be able to participate, thus saving time. Any business or company should do as many tests as possible for accuracy.

Testing in a professional environment.
In a professional environment, 2 labs should be hired with a very large mirrored wall in-between them. The owners, inventors or developers watch from one lab to the other and observe the person and the prototype tested.

Simple testing without using professionals.
Use one room with at least 2 cameras to record the person and product being tested, which will be used later with the owners, inventors or developers.

The problem with simple testing is the professional environment can be costly to businesses. Compared to simple testing, it’s far cheaper and flexible for businesses and the people involved.