Tag Archives: compatibility

12 SOFTWARE TESTING TECHNIQUES YOU CAN APPLY IN WEB DESIGN


12 Software Testing Techniques applied in Web Design

The web design industry has been taken by storm lately. There are tons of new comers every year bringing their style and creativity on the table. But you gotta admit that some of the work is quite below par. Coding issues, UI mismatch and worst of all UX problems are prevalent among them. Now if you’re from an I.T field you’re bound to have come across the term called software testing. They’re a string of testing techniques for those cumbersome JAVA and .NET softwares before deploying them live or before submitting them for grades :)

It struck me just the last time while handling the design of a WordPress portal that why can’t we implement those testing methods on our web design projects. I took some of the most essential testing methods ranging from basic to intermediate and found fabulous results which I’d like to share with you’ll. We’ll go through the testing techniques which I leveraged upon my project and learn how can we improve from our errands.


Black Box Testing

Just scraping the surface and looking for the overall functionality and design errors without worrying about the internal working. If any found, it’s suggested to correct them at this very stage.


White Box Testing

Also known as Glass Box Testing, this one’s based upon the building blocks of the project’s code. The person in charge for this type of testing is expected to carry sound knowledge of the programming language used for the back-end to make sure our project doesn’t have any syntax errors.


Acceptance Testing

Usually this type of testing is done to check whether all of the client’s requirements have been fulfilled or not. An important thing to remember here is that the client does this testing to decide whether to accept the project as satisfactory or not.

Fork CMS


Usability Testing

With this type of testing the designer can test whether UX has been respected or not. Can your client handle and manage your project without any hassle? If not proper documentation to guide him should be included.


Compatibility Testing

Usually this type of testing is done to check whether the application performs equally well in various software environments and operating systems which a web designer can undertake to make sure whether the website looks and functions similarly in all major browsers, for which the technical term is cross-browser testing.


Comparison Testing

A comparison of your current and previously successful project can help you make out its strengths as well as weaknesses and work upon them to improve it.


Regressions Testing

This type of testing is used when you’re gonna release sequential versions of your theme or design. It can help you to overcome previous errors and not to repeat them while releasing next versions.

Stepehn Gacheru Portfolio


Load Testing

As the name suggests, this type of testing can be performed to check the status of your project under heavy loads. For example you can check the loading time when a number of plugins have been installed or the response time under complicated database queries.


Performance Testing

A mixture of Load and Stress testing, this method can be used to check whether your project meets the performance requirements and under what conditions does it give best results.


Integration Testing

Most of us designers and developers take up a project and develop it step by step in parts or modules. In the end all of them are connected to each other and what you get is the final result. This type of testing is done to verify the combined functionality after the integration of all those modules.


Recovery Testing

God forbidden but if at all your CMS fails, this type of testing is done to check how well does it recover from such failures. Always make a back up before deploying any of your project.


Security Testing

Due to a large number of hackers at large, this type of testing becomes very necessary to check whether your project is safe from unauthorized access. Even a minor flaw can allow the attackers to inject an SQL string and corrupt your database. Make it ‘almost’ impenetrable before setting it live.

                And there they are. The above mentioned are the twelve testing methods used in software testing which I executed upon my web design projects before they go live. We can make sure that our designs are almost perfect and in excellent functional status and minimize the rise of errors as much as possible. Shoot up your opinions down in the comments.

Source:http://blogverize.blogspot.com/2012/06/12-software-testing-techniques-you-can.html

Did you like this? Share it:

Test Factors in Software Testing

Introduction

For designing Test Cases the following factors are considered:

  1. Correctness
  2. Negative
  3. User Interface
  4. Usability
  5. Performance
  6. Security
  7. Integration
  8. Reliability
  9. Compatibility

Correctness : Correctness is the minimum requirement of software, the essential purpose of testing. The tester may or may not know the inside details of the software module under test e.g. control flow, data flow etc.

Negative : In this factor we can check what the product it is not supposed to do.
User Interface : In UI testing we check the user interfaces. For example in a web page we may check for a button. In this we check for button size and shape. We can also check the navigation links.
Usability : Usability testing measures the suitability of the software for its users, and is directed at measuring the following factors with which specified users can achieve specified goals in particular environments.

  1. Effectiveness : The capability of the software product to enable users to achieve specified goals with the accuracy and completeness in a specified context of use.
  2. Efficiency : The capability of the product to enable users to expend appropriate amounts of resources in relation to the effectiveness achieved in a specified context of use.

Performance : In software engineering, performance testing is testing that is performed from one perspective to determine how fast some aspect of a system performs under a particular workload.
Performance testing can serve various purposes. It can demonstrate that the system needs performance criteria.

  1. Load Testing: This is the simplest form of performance testing. A load test is usually conducted to understand the behavior of the application under a specific expected load.
  2. Stress Testing: Stress testing focuses on the ability of a system to handle loads beyond maximum capacity. System performance should degrade slowly and predictably without failure as stress levels are increased.
  3. Volume Testing: Volume testing belongs to the group of non-functional values tests. Volume testing refers to testing a software application for a certain data volume. This volume can in generic terms be the database size or it could also be the size of an interface file that is the subject of volume testing.

Security : Process to determine that an Information System protects data and maintains functionality as intended. The basic security concepts that need to be covered by security testing are the following:

  1. Confidentiality : A security measure which protects against the disclosure of information to parties other than the intended recipient that is by no means the only way of ensuring
  2. Integrity: A measure intended to allow the receiver to determine that the information which it receives has not been altered in transit other than by the originator of the information.
  3. Authentication: A measure designed to establish the validity of a transmission, message or originator. Allows a receiver to have confidence that the information it receives originated from a specific known source.
  4. Authorization: The process of determining that a requester is allowed to receive a service/perform an operation.

Integration : Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested.

Reliability : Reliability testing is to monitor a statistical measure of software maturity over time and compare this to a desired reliability goal.

Compatibility : Compatibility testing of a part of software’s non-functional tests. This testing is conducted on the application to evaluate the application’s compatibility with the computing environment. Browser compatibility testing can be more appropriately referred to as user experience testing. This requires that the web applications are tested on various web browsers to ensure the following:

Users have the same visual experience irrespective of the browsers through which they view the web application.

In terms of functionality , the application must behave and respond the same across various browsers.

Source:http://www.c-sharpcorner.com/UploadFile/face6d/test-factors-in-software-testing/

Did you like this? Share it:

Types of software Testing

Software Testing Types:

Black box testing – Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.

White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.

Unit testing – Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.

Incremental integration testing – Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.

Integration testing – Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Functional testing – This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.

System testing – Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.

End-to-end testing – Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Sanity testing - Testing to determine if a new software version is performing well enough to accept it for a major testing effort. If application is crashing for initial use then system is not stable enough for further testing and build or application is assigned to fix.

Regression testing – Testing the application as a whole for the modification in any module or functionality. Difficult to cover all the system in regression testing so typically automation tools are used for these testing types.

Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customer do this testing to determine whether to accept application.

Load testing – Its a performance testing to check system behavior under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.

Stress testing – System is stressed beyond its specifications to check how and when it fails. Performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system or database load.

Performance testing – Term often used interchangeably with ‘stress’ and ‘load’ testing. To check whether system meets performance requirements. Used different performance and load tools to do this.

Usability testing – User-friendliness check. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing.

Install/uninstall testing - Tested for full, partial, or upgrade install/uninstall processes on different operating systems under different hardware, software environment.

Recovery testing – Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Security testing – Can system be penetrated by any hacking way. Testing how well the system protects against unauthorized internal or external access. Checked if system, database is safe from external attacks.

Compatibility testing – Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.

Comparison testing – Comparison of product strengths and weaknesses with previous versions or other similar products.

Alpha testing – In house virtual user environment can be created for this type of testing. Testing is done at the end of development. Still minor design changes may be made as a result of such testing.

Beta testing – Testing typically done by end-users or others. Final testing before releasing application for commercial purpose.

source: http://www.softwaretestinghelp.com/types-of-software-testing/

Did you like this? Share it:

12 Best Cross Browser Testing Tools to Ease Your Browser Compatibility Testing Efforts

Cross Browser Testing can be the biggest pain for Software testers. But thanks to all cross browser testing tools available online which help to minimize testing efforts.

I’ve written this post mainly for software testers but designers can also refer cross browser testing methods and tools mentioned in this post.

Here’s a handy cross browser testing checklist you can refer while testing your web project on different browsers and operating systems:

1) CSS validation
2) HTML or XHTML validation
3) Page validations with and without JavaScript enabled
4) Ajax and JQeury functionality
5) Font size validation
6) Page layout in different resolutions
7) All images and alignment
8 ) Header and footer sections
9) Page content alignment to center, LHS or RHS
10) Page styles
11) Date formats
12) Special characters with HTML character encoding
13) Page zoom-in and zoom-out functionality

And obviously you will have to repeat these tests on:
14) Different Operating Systems like Windows, Linux and Mac
15) Different browsers (with different versions) like Internet explorer, Firefox, Google Chrome, Safari and Opera.

There are many free and paid cross browser testing tools available in the market. You need to select the browser compatibility tool depending on your needs. If cross browser testing is critical part of your web project then you must allocate considerable time, resources and budget testing your website on different web browsers. Paid cross browser testing tools can be also a good option for projects having browser dependent functionality. But for most of the projects, free cross browser testing tools are sufficient to verify cross browser functionality

Free Cross Browser Testing Tools:

1) Spoon Browser Sandbox:

2) Browsershots

3) IE NetRenderer

4) IE Tab

5) IE Tester

6) Microsoft SuperPreview

Paid Cross Browser Testing Tools:

7) Browsera

8 ) Adobe BrowserLab

9) BrowserCam

10) Browserseal

11) Cross Browser Testing

12) Cloud Testing

Source: http://www.softwaretestinghelp.com/best-cross-browser-testing-tools-to-ease-your-browser-compatibility-testing-efforts/

Did you like this? Share it: