Tag Archives: box

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:

White Box and Black Box Test Cases

To write black box test cases software tester needs the requirement document and design plan. These documents are easily accessible at the very beginning of the project.

At the same time white box test cases cannot be written at the initial start of the project. It is so because white box test cases need more architecture clearness which is not accessible at the beginning of the project.

White Box and Black Box Test Cases

So it is a common situation when white box test cases are written after black box ones.

Black box test cases don’t need system comprehension but white box testing requires more structural comprehension.

Structural comprehension is more intelligible in the later stages of project.

For black box testing QA engineer needs to only analyze from the functional perspective which is easily accessible from a simple requirement document.

Source: http://www.vietnamesetestingboard.org/zbxe/?mid=download&category=12675&document_srl=588605&listStyle=&cpage=

Did you like this? Share it:

Glass Box: The Next Phase of Web Application Security Testing?

For years, security researchers have used the terms "black box" and "white box" to describe dynamic and static web application security analysis, respectively. IBM is now seeking to combine the best of both approaches by introducing a new approach called "Glass Box."

"We use the terms ‘black box’ and ‘dynamic analysis’ interchangeably, and basically that’s looking at a functioning application in a web browser and evaluating its state to identify potential vulnerabilities," Patrick Vandenberg, program director for IBM Security, told InternetNews.com. "’Static analysis’ we use interchangeably with white box testing and that’s looking at source code before it is compiled to root out potential vulnerabilities."

IBM historically has provided black box testing by way of its AppScan portfolio. AppScan was expanded in 2010 with a source code edition that can do static, white box analysis.

With its latest release of AppScan standard edition 8.5, IBM is now taking that capability one step further by introducing the new Glass Box approach. With Glass Box, AppScan installs agents on a server to instrument the code, while also applying dynamic analysis techniques.

"In so doing we’re getting the real-world validation that you get from black box testing as well as getting inside the box, and that delivers phenomenal improvements in accuracy," Vandenberg said.

When it comes to root cause analysis using Glass Box, Vandenberg noted that users are limited in what they can see from an instrumentation perspective. That said, Vandenberg added that the system is able to provide coverage for all the vulnerabilities that a user would be able to find from a static analysis perspective within the context of a web application.

Full static analysis is still required for non-web applications as well as from a process perspective.

"Really the root cause is sitting in development where all these vulnerabilities are first introduced to the code," Vandenberg said. "You want to find those flaws as early as you can."

IBM also has production software capabilities with its Tivoli software division that could benefit from the enhanced security analysis that Glass Box can provide.

"We can push the vulnerability data there so that policies can be tuned and pushed out to all the devices that are being managed," Vandenberg said.

Source: http://www.esecurityplanet.com/network-security/glass-box-the-next-phase-of-web-application-security-testing.html

Did you like this? Share it:

Brief Introduction of the book “A Software Testing Primer”

Here we will mainly introduce the book “A Software Testing Primer” by Nick Jenkins. Thus, you will get basic idea of manual and automation testing. Fisrtly, let’s have a glance of what this book is covering:

1. What is the need of software testing?

2. Different software defelopment models

3. Testing in the software development life cycle

4. How to develop testing mindset?

5. Regression VS. Retesting

6. White box VS. Black box testing

7. Verification and validation

8. Alpha and beta testing

9. Unit, Integration and System testing

10. Acceptance testing

11. Automation testing – Basics

12. Testing the design

13. Usability testing

14. Performance testing

15. Test planning

16. Test estimation

17. Test cases and elements of test cases

18. Test tracking, Test planning and Test plan review

19. How to manage defects and defect reports?

20. Test metrics for testers

21. Product release control

All points above nicely introduce software testing. Moreover, Regression and Retesting difference, Alpha and beta testing and other points that many testers confuse, the author also has good explainations to them.

Source: http://www.softwaretestinghelp.com/software-testing-book-download/

Did you like this? Share it:

Application Testing – Into the Basics of Software Testing

Every software tester performs application Testing daily in his career. And today here we’ll get a brief understanding of application testing.

There are two kinds of applications: desktop and web. For desktop applications, testing should consider the UI, business logic, databade, reports, roles and rights, integrity, usability and data flow. Then while for web applications, testers should pay more attention to performance, load and security of the application. Therefore, AUT is either desktop software or a website.

Today only three universal application testing methodologies are accepted: Black Box, White Box, and Grey Box. However, application testing tools are various. Here we list some most improtant and fundamental features of the functional testing tools:

1. Record and Play

2. Parametrize the Values

3. Script Editor

4. Run (the test or script, with debug and update modes)

5. Reprot of Run session

Application Testing cycles includes Somke Testing, Sanity Testing, Functional Testing, and Regression Testing. Application Testing is a vast subject and the primary activity of any software tester.

Source: http://www.softwaretestinghelp.com/application-testing-%E2%80%93-into-the-basics-of-software-testing/

Did you like this? Share it:

Thinking out of the box & software testing

We always hear a phrase “Creative thinking” or “Out of the box thinking”. The actual meaning of it is to think differently, unconventionally or from a new perspective, especially referred to novel and creative thinking. However, the definition could be extended when it comes to software testing.

Nowadays the first thing of software testing is Two Boxes, a white box and a black box. As a result, all we do is either black bos or white box testing, which has limited our mind from thinking beyond the boxes. Hence, going beyond these may help us gaining a higher pace towards a solid career in software testing.

Source: http://www.softwaretestinghelp.com/thinking-out-of-the-box-while-testing-software/

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:

Gray Box Testing

Testing Types – System Knowledge

Grey box testing is the combination of black box and white box testing. Intention of this testing is to find out defects related to bad design or bad implementation of the system.

In gray box testing, test engineer is equipped with the knowledge of system and designs test cases or test data based on system knowledge.

For example, consider a hypothetical case wherein you have to test a web application. Functionality of this web application is very simple, you just need to enter your personal details like email and field of interest on the web form and submit this form. Server will get this details, and based on the field of interest pick some articles and mail it to the given email. Email validation is happening at the client side using Java Scripts.

In this case, in the absence of implementation detail, you might test web form with valid/invalid mail IDs and different field of interests to make sure that functionality is intact.
But, if you know the implementation detail, you know that system is making following assumptions

  • Server will never get invalid mail ID
  • Server will never send mail to invalid ID
  • Server will never receive failure notification for this mail.

So as part of gray box testing, in the above example you will have a test case on clients where Java Scripts are disabled. It could happen due to any reason and if it happens, validation can not happen at the client site. In this case, assumptions made by the system are violated and

  • Server will get invalid mail ID
  • Server will send mail to invalid mail ID
  • Server will receive failure notification

Hope you understood the concept of gray box testing and how it can be used to create different test cases or data points based on the implementation details of the system.

source: http://www.testinggeek.com/index.php/testing-types/system-knowledge/51-grey-box-testing

Did you like this? Share it: