Havard: Testing Idea

Havard. Testing,Career

The Surprising Fit for Software Testing

Handy Special Characters

Often we need to test the application behavior with special characters. Here is the list of special characters

 

 

French: áàâéèçêùÉÇÈÊÂô
German: äëïöüÄËÏÖÜß
Danish: øæåéØ
Norwegian: øæåéØ
Finnish: ÄäÖö
Swedish: åÄÖö
German: ÖÄÜöäüß
French: éèêàâÉç
Italian: èùà
Spanish: áóíóúñÁÉÍÓÚ
Dutch: ëéöú
Portuguese: çãàáãêéóõíú Ã

Other CE languages:

Polish: śąńężóćŹ
Czech: áéěřčůžýíďůžŠhjbgi ghilugiu
Slovakian: áéěřčůžýíďůžŠ
Russian: no special characters, separate alphabet - Cyrillic alphabet
example: Компании, которые приобретают, уже используют или переходят на

Greek: αβγδεζηθικλμνζοπρσςτυφχψω
ΑΒΓΔΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΩ
Hungarian: Áá Éé Íí Óó Öö Őő Úú Üü Űű
[Treated as single letters] CS cs DZ dz DZS dzs GY gy LY ly NY ny SZ sz TY ty ZS zs
Turkish: Çç Iı Öö Şş Üü ğ

año.tif

Copyright symbol = ©©©©©©©©©©©©©©

šrčrřtřt
ěšč

Award of New Attacks

This summary is not available. Please click here to view the post.

Fault Injection Part 1

Fault Injection,Fuzzing,Fuzz

Title looks interesting for any software tester.

Can we inject fault in software.?

Answer is yes, Fuzzing approach allows to inject fault in a application. What fuzzing is all about.  Fuzzing testing is the approach of testing which is being carried out when testing process was not well organized and interestingly it is still alive.

From Wikipedia Fuzz testing or fuzzing is a software testing technique that provides random data ("fuzz") to the inputs of a program. If the program fails (for example, by crashing, or by failing built-in code assertions), the defects can be noted.

There are several tools and frameworks available for Fuzzing testing. Links to some of them are

http://peachfuzz.sourceforge.net/

http://gunzip.altervista.org/

http://www.spidynamics.com/products/webinspect/toolkit.html

Beside them, there are n numbers of automation tools available for all this.

For successfully fuzzing we should follow following points:

1. Number of iteration should be high: If fuzzing finds a bug it should not be stopped as it is only pointing a weak area in the application which calls for more attention or testing

2. Interesting data should be fuzzed while keeping the overall data format intact

3. So as fuzzing is providing a random data in large ability to weed out the duplicate bug

4. Record of data that caused the problem for reproducibility

5. Getting to base state if and when required

 

 

 

 

Flag OFF

Here Goes my First Post.