Tag Archives: black

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:

Software Testing – Black Box Testing Strategy

Black Box Testing is not a type of testing; it instead is a testing strategy, which does not need any knowledge of internal design or code etc. As the name “black box” suggests, no knowledge of internal logic or code structure is required. The types of testing under this strategy are totally based/focused on the testing for requirements and functionality of the work product/software application. Black box testing is sometimes also called as “Opaque Testing”, “Functional/Behavioral Testing” and “Closed Box Testing”.
The base of the Black box testing strategy lies in the selection of appropriate data as per functionality and testing it against the functional specifications in order to check for normal and abnormal behavior of the system. Now a days, it is becoming common to route the Testing work to a third party as the developer of the system knows too much of the internal logic and coding of the system, which makes it unfit to test the application by the developer.
In order to implement Black Box Testing Strategy, the tester is needed to be thorough with the requirement specifications of the system and as a user, should know, how the system should behave in response to the particular action.
Various testing types that fall under the Black Box Testing strategy are: functional testing, stress testing, recovery testing, volume testing, User Acceptance Testing (also known as UAT), system testing, Sanity or Smoke testing, load testing, Usability testing, Exploratory testing, ad-hoc testing, alpha testing, beta testing etc.
These testing types are again divided in two groups: a) Testing in which user plays a role of tester and b) User is not required.

Testing method where user is not required:

Functional Testing:
In this type of testing, the software is tested for the functional requirements. The tests are written in order to check if the application behaves as expected.
Stress Testing:
The application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries etc. which checks for the stress/load the applications can withstand.
Load Testing:
The application is tested against heavy loads or inputs such as testing of web sites in order to find out at what point the web-site/application fails or at what point its performance degrades.
Ad-hoc Testing:
This type of testing is done without any formal Test Plan or Test Case creation. Ad-hoc testing helps in deciding the scope and duration of the various other testing and it also helps testers in learning the application prior starting with any other testing.
Exploratory Testing:
This testing is similar to the ad-hoc testing and is done in order to learn/explore the application.
Usability Testing:
This testing is also called as ‘Testing for User-Friendliness’. This testing is done if User Interface of the application stands an important consideration and needs to be specific for the specific type of user.
Smoke Testing:
This type of testing is also called sanity testing and is done in order to check if the application is ready for further major testing and is working properly without failing up to least expected level.
Recovery Testing:
Recovery testing is basically done in order to check how fast and better the application can recover against any type of crash or hardware failure etc. Type or extent of recovery is specified in the requirement specifications.
Volume Testing:
Volume testing is done against the efficiency of the application. Huge amount of data is processed through the application (which is being tested) in order to check the extreme limitations of the system.

Testing where user plays a role/user is required:


User Acceptance Testing:
In this type of testing, the software is handed over to the user in order to find out if the software meets the user expectations and works as it is expected to.
Alpha Testing:
In this type of testing, the users are invited at the development center where they use the application and the developers note every particular input or action carried out by the user. Any type of abnormal behavior of the system is noted and rectified by the developers.
Beta Testing:
In this type of testing, the software is distributed as a beta version to the users and users test the application at their sites. As the users explore the software, in case if any exception/defect occurs that is reported to the developers.

source: http://www.buzzle.com/editorials/4-10-2005-68349.asp

Did you like this? Share it: