Software Testing Winners

Quality Center (9.2)

2010-12-01T20:44:00.000-08:00

Important notes about Quality Center (9.2):

Modules:

Releases
Requirements
Test Plan
Test Lab
Defects

Priority:

Resolve immediately,
High,
Normal,
Low.

Severity:

Critical,
High,
Medium,
Low

Status:

Assigned,
Closed,
Deferred,
Fixed,
New,
Open,
Ready for retest,
Rejected,
Reopen,
Request for deferral,
Requirement Evaluation,
Unassigned

New Defect:

Mandatory Fields while posting a defect:

Summary
Application Area,
Defect Type,
Detected in version,
Environment
Priority
Status
Customer Issue
Detected By
Detected on date
Focus Area
Reproducible
Description
Screenshot

Non Mandatory fields:

Cost estimate in dollars
Customer name
Detected in Release
Estimated fix time
Severity
Target release
Assigned to
Current production issue
Detected in cycle
Escalation
Resolved by
Target cycle

Attachment options:

File attachment
Camera capture 9snapshot)
Attach URL
Attach system info
Attach clip content

Roles of QA in Requirement Analysis Phase of SDLC

2010-06-14T22:58:00.000-07:00

Requirement Analysis:

It is the first phase of Software Development Life Cycle and so important too, since defects can be found early through this phase.Generally it will be done by both dev team and the qa team. Both teams will analyze the requirements documents from the client.
This document will be prepared by Business Analyst who is having thorough rapport with the client regarding their requirements.

Documents

This Requirement document contains the following files,

1) Functional Specification
2) Mock ups
3) Data Layouts

Roles of QA

1) Take the FS as a baseline document and analyze each and every page of it
2) If any clarification needed on any particular functionality or any suggestions to implement the features or any logical issues, then raise a defect or clarification against the Functional Specification document
3) Track the defect or clarification raised against the FS
4) If it is addressed, check whether it is updated in the base line document
5) Check whether the updated functional specification is available for all stake holders with the latest version
6) Check whether the version history is updated with change date and the author name who made changes in the document
7) Sign off from RA phase

Basic Unix Commands

2010-05-31T23:59:00.000-07:00

ls ................. show directory, in alphabetical order
logout ............. logs off system
mkdir .............. make a directory
rmdir .............. remove directory (rm -r to delete folders with files)
rm ................. remove files
cd ................. change current directory
man (command) ...... shows help on a specific command
talk (user) ........ pages user for chat - (user) is a email address
write (user) ....... write a user on the local system (control-c to end)

pico (filename) .... easy to use text editor to edit files
pine ............... easy to use mailer
more (file) ........ views a file, pausing every screenful

sz ................. send a file (to you) using zmodem
rz ................. recieve a file (to the unix system) using zmodem

telnet (host) ...... connect to another Internet site
ftp (host) ......... connects to a FTP site
archie (filename) .. search the Archie database for a file on a FTP site
irc ................ connect to Internet Relay Chat
lynx ............... a textual World Wide Web browser
gopher ............. a Gopher database browser
tin, trn ........... read Usenet newsgroups

passwd ............. change your password
chfn ............... change your "Real Name" as seen on finger
chsh ............... change the shell you log into

grep ............... search for a string in a file
tail ............... show the last few lines of a file
who ................ shows who is logged into the local system
w .................. shows who is logged on and what they're doing
finger (emailaddr).. shows more information about a user
df ................. shows disk space available on the system
du ................. shows how much disk space is being used up by folders
chmod .............. changes permissions on a file
bc ................. a simple calculator

make ............... compiles source code
gcc (file.c) ....... compiles C source into a file named 'a.out'

gzip ............... best compression for UNIX files
zip ................ zip for IBM files
tar ................ combines multiple files into one or vice-versa

Some Basic SQL Queries

2010-03-12T07:49:00.000-08:00

1) Query to select Maximum Salary from a Table

Select Max (ActualSalary) from employees

2) Query to select Minimum Salary from a Table

Select Min (ActualSalary) from employees

3) Query to select unique values from a table

Select Distinct EmpStatusCode from employees

4) Query to select 6th highest Salary

SELECT TOP 1 ActualSalary
FROM (SELECT DISTINCT TOP 6 ActualSalary FROM employees
ORDER BY ActualSalary DESC) a
ORDER BY ActualSalary

5) Query to select total count from table

SELECT count (* or field name) from employees

6) Query for ascending order display

SELECT * from employees Order by LastName

7) Query for Descending Order display

SELECT * from employees Order by LastName DESC

8) Query to insert Values into a table

INSERT INTO Persons (P_Id, Last Name, FirstName)
VALUES (5, 'Tjessem', 'Jacob')

9) Query to update values in a table

SET EmpID =1000 WHERE LastName=’Rakesh’

10) Query to delete a value from a table

Delete from employees where EmpID=1000

If you know some basic queries other than this, kindly drop it in the comment section.

Importance of Resolution Testing

2010-03-12T07:24:00.000-08:00

Few Days back we got a bug from our client when the application was in Production Server.They got java script error and blank page while accessing a particular menu. (Find the Screen shot below)

It was straightly forwarded to the development team by our project manager.
They tried many times to reproduce the issue but they can’t.At last as usual it came to our testing team and we also tried to reproduce the same and failed.

We tried in lot of scenarios and by changing the system environment also.
At Last we changed our screen resolution into 800 * 600 pixels and tried to access the same menu which was reported by our client and we got the same error this time.

At that day we learnt a lesson to test the application by changing the screen resolution.After that we had added this scenario into our lesson learnt document and also in Test Scenario document.

Many of us were aware of this type of Resolution Testing. But due to lack of schedule we missed to execute these scenarios and these things will become very big issues to the client.

So make sure to test the application by changing the screen resolution before delivering the application to the client.

If you have any feedbacks for this post, kindly drop it in the comment section

Testing Interview Questions

2009-06-24T23:27:00.000-07:00

If you are going to attend an interview in Manual Testing, then you have to prepare for the following basic questions which were asked in many interviews.

1) Prepare about you and your professional experience. It will be within 3 to 5 minutes.
2) Prepare something about your company details
3) Your Roles and Responsibilities in your company
4) Prepare about your current project. You have to tell the Project title, Client of the project, Short Description about the project, how many modules are there in the project and which part you have involved in the project.
5) Your Daily Regular activities after entering and leaving from office?
6) Types of testing u have done in your experience?
7) What are the challenges situations you have faced?
8) What are Severity and priority and some examples?
9) What are all the achievements you made in your company in your role?
10) What are all the challenging defects you found?
11) What will you do to reproduce issues, if the developer says that he can’t able to reproduce?
12) How will you Communication within your team and stake holders?
13) What is the Difference between client server applications and Web Applications?
14) What is SDLC and explain about it?
15) What is STLC and explain about it?
16) Testing process you follow in your company?
17) What is Bug life cycle and explain about it?
18) Test case preparation and sample test cases?
19) What is Requirement traceability matrix and how will you do it in your company?
20) What is Defect traceability matrix?
21) How does a web applications works?
22) What is V- Model and explain about it?
23) What is the Difference between waterfall model and V MODEL?
24) What are all the Testing Techniques?
25) What is Boundary Value analysis and Equivalence partitioning and give examples?

If you people have more questions that will be asked in interviews, kindly add it in the comments section.

Severity and Priority of Defects

2009-06-24T06:56:00.000-07:00

Generally we have to set the Severity and Priority level for a Defect. Severity level will be set by the Testing Team and the Priority level will be set by the Development Team.

Severity means how much severe is the particular defect in the application (i.e.) how it affects the functionality of the application

Priority means the importance and urgency to fix the defect by the developers (i.e.) which defect should be fixed first and which should be fixed in later versions.

There and some levels in severity and priority, they are as follows….

Severity levels:

Trivial
Minor
Major
Critical
Block

Priority Levels:

Low
Medium
High
Urgent
Immediate

The Severity and Priority levels must vary depends upon the company and the defect tracking tool used by the company.

Some Examples for the priority levels….

Low Priority: Spelling mistakes, grammatical errors, Textual Errors, Orphan pages, broken links, GUI errors,

High Priority: Wrong Functionality, Applications Crashes, Errors

If you have any feed backs for this post, kindly drop it in the comments section.

Details to be given while posting a Defect

2009-06-14T09:53:00.000-07:00

I know that all the experienced Testers must have knowledge on what are all the details that should be given to a developer while posting a defect. But I am writing this article for fresh testers. Anyway experienced testers, write down your comments, feed backs and valuable points which can be added from your experience. It will be more helpful for the fresh peoples who are reading this article.

1) Category of the defect
2) Defect Reproducibility
3) Severity of the defect
4) Version of the product/project
5) OS Version
6) Environment Details
7) Summary of the defect
8) Description
9) Steps to Reproduce
10) Additional Information
11) Login Details
12) Test Data
13) Actual Result
14) Expected Result
15) Screen shots for proof
16) Videos if any for reproduce

Roles and Responsibilities of a "Software Testing Engineer"

2009-06-10T23:53:00.000-07:00

Generally Roles and Responsibilities of a Testing Engineer may vary, depending upon the working company. But here we are going to discuss about the general and important roles and responsibilities of a Testing Engineer.

1) Analyzing the Requirements from the client
2) Participating in preparing Test Plans
3) Preparing Test Scenarios
4) Preparing Test Cases for module, integration and system testing
5) Preparing Test Data’s for the test cases
6) Preparing Test Environment to execute the test cases
7) Analyzing the Test Cases prepared by other team members
8) Executing the Test Cases
9) Defect Tracking
10) Giving mandatory information of a defect to developers in order to fix it
11) Preparing Summary Reports
12) Preparing Lesson Learnt documents from the previous project testing experience
13) Preparing Suggestion Documents to improve the quality of the application
14) Communication with the Test Lead / Test Manager
15) Conducting Review Meetings within the Team

These are the Roles and Responsibilities of a Testing Engineer which is based upon my knowledge. If you know more about this kindly write it down in the comments section.
Your Feed backs are welcome!

Expert Rating Certification in Software Testing

2009-05-09T05:39:00.000-07:00

Here comes another one certification for Software Testing, "Expert Rating".
While comparing with other certifications it is very cheap and i don't know how worth is this certification
in India. But i am sure that it will increase our confidence level in our "Software Testing" field.

Syllabus for this certification :

1) Fundamentals concepts in software testing
2) Advanced Testing concepts
3) Types of Testing
4) Automation Testing

Fees and Payment Details :

Charges for taking up this certification is 9.95 USD and they are charging 5 USD for hard copy of your certificate.

You can pay the fee by using credit/debit cards and take the exam in online.

Question Types:

There will be 40 multiple choice questions and 40 minutes duration for the exam.
No negative mark is given for your wrong answers. You have to get 50 % to pass the exam.

For more details kindly visit : http://www.expertrating.com/certifications/Software-Testing-Test.asp

There are other useful certifications available for software professionals in this site, for more details visit : http://www.expertrating.com/certifications.asp

I Have completed this certifications and got my logo, Kindly view my Transcript Details in the below link,
http://www.expertrating.com/transcript.asp?transcriptid=2253348

Basic SQL Commands

2009-05-09T05:22:00.000-07:00

DDL

DDL (Data Definition Language) statements are used to define the database structure or schema. Some examples:

• CREATE - to create objects in the database
• ALTER - alters the structure of the database
• DROP - delete objects from the database
• TRUNCATE - remove all records from a table, including all spaces allocated for the records are removed
• COMMENT - add comments to the data dictionary
• RENAME - rename an object

DML

DML (Data Manipulation Language) statements are used for managing data within schema objects. Some examples:
• SELECT - retrieve data from the a database
• INSERT - insert data into a table
• UPDATE - updates existing data within a table
• DELETE - deletes all records from a table, the space for the records remain
• MERGE - UPSERT operation (insert or update)
• CALL - call a PL/SQL or Java subprogram
• EXPLAIN PLAN - explain access path to data
• LOCK TABLE - control concurrency

DCL

DCL is Data Control Language statements. Some examples:
• GRANT - gives user’s access privileges to database
• REVOKE - withdraw access privileges given with the GRANT command

Benefits Of Certification

2009-04-03T02:13:00.000-07:00

In this time of "Recession" all the professionals are doing certification in their fields.Here we will discuss about the benefits of doing certification in software testing field.

1) Increases Company Reputation
2) Recognition by IT management for professional achievement
3) Competency resources to IT staff
4) Helpful for Marketing with the clients
5) Increased Confidence in Personal Capabilities
6) Improved Software Testing Methods, Techniques, and Measurement
7) Certification gives you a competitive edge for promotion and hiring.
8) Raises profile of testing in an organization
9) Able to detect defects those others miss and save your employers and clients from costly and embarrassing field failures.
10)Knows how to apply sound software testing techniques
11)Reduced development costs
12)Increased customer trust and confidence
13)We understood the software life cycle
14)Quality of the defect has been increase
15)Understood the testing terminology
16)Increase the standard for defect post
17)Started thinking out of the box
18)Increase in Communication
19)Testing based on the risk factors
20)We started concentrating on usability
21)Started conducting meeting and reviews
22)Soft skills (e.g. handling the development team)
23)Updated the process/frame work
24)Increase the type of testing. (e.g. compatibility)

If i missed out any benefits, please add that in the comments field.

Habits of Highly Effective Negative Testers

2009-03-24T03:44:00.001-07:00

1) First check if all the tabs, menus and links are displaying proper pages
2) Put negative numbers into text fields
3) Put ridiculously long strings anywhere you can,
4) Paste inappropriate stuff - like binary files into text boxes
5) Open 13 instances of your app at once
6) Unplug the network or the power in the middle of an important flow
7) Change the system date and time
8) Install on a system way below the minimum specs
9) Use weird characters like ì È Ö
10) Run 10 other apps while you are testing
11) Delete crucial files
12) Don't close other applications before proceeding
13) Press submit button in all the forms for more than one time and see
the application response
14) Try to login with case sensitive passwords
15) Close your Browser while doing any uploading or submitting in the application
16) Test with low bandwidth networks
17) Change the parameter id’s displayed in the URL
18) View for Application icon in browser address bar
19) Check with the displayed error messages through out the application
20) Check whether the user can find on which page he is now (i-e) Application
have to highlight the current page

Tips to Capture “Unable to reproduce issues”

2009-03-20T02:48:00.000-07:00

A Very challenge thing to a Software Tester is if he posted one critical issues by spending more time, then the developer will simply add comment as “Unable to reproduce”.
At this stage we have to fight with the developer by adding more screenshots or by conducting meetings to explain how to reproduce the issue.
Now a simple way comes to capture a defect in the application. Using this we can record how to reproduce the issue.

http://www.screentoaster.com/

1) Go to the above site and register as a new user
2) Login to the application and click Start Recording button
3) It will display Record button
4) Now go to your application and click “Alt+S”
5) Try your scenario to reproduce the issue
6) After reproducing the issue click “Alt+S” and go to screen toaster
7) Click stop recording
8) Now the video to reproduce your issue is ready to view

You can upload the video into screen toaster and you will get a URL for that
You can upload it in YouTube
You can download the video in “AVI” and “SWF” formats

Now attach the video or give the link while reporting the issue. Developers will not say “Unable to reproduce” after seeing this video.

For your reference I have attached a video to explain about how to record a video to capture an issue.
I have recorded the scenario in login page of “YouTube”

http://www.screentoaster.com/watch/stU0ldRkRIR1pYRVlcXF9RUFVX/how_to_record_a_video

“Happy Testing”

Useful Tips for Testing

2009-03-20T02:05:00.000-07:00

In this article we can discuss about some useful tips that are used for software testing.
While testing a web application, there will be some clone sites available for that application.
First we need to check the functionality of the clone site to know more about the application. At that time we need to register in that clone site and then only we can able to proceed. But now a site is giving sample login details for all the famous sites. Link for the site is

http://www.bugmenot.com/

Using this site we can get sample login details for any popular sites and it will be more useful while testing.
For Ex: If you are going to study about the functionality of “YouTube”, but you don’t have login details for YouTube. At this time you can use this above site to get sample details for YouTube.
Check out some sample login details in the below link,

http://www.bugmenot.com/view/youtube.com

Using this logins you can enter into “YouTube” as a registered user.

Categories of Defect

2009-03-16T03:51:00.000-07:00

While posting a defect we have to choose appropriate category for the defect.
If you are using any bug tracking tool, then it will be mandatory to select category for the defect while posting. Here we can see how many categories are available for a defect,

1) Functionality Issues
2) Logical Issues
3) Designing Issues
4) Flash Issues
5) Errors
6) Compatibility Issues
7) Usability Issues
8) User Interface Issues
9) Textual Errors
10)Documentation Issues
11) Validation Errors
12) Feature Additional
13) Suggestions
14) Query
15) Enhancements

If you know more categories of defects, kindly write down in comments section or send an e-mail to me.

User Interface Testing

2009-03-12T00:05:00.000-07:00

User Interface Testing:

User interface testing is defined as to test the interface between the application and the end user.
Here we will see how to test a simple form for user interface testing.

Steps for User Interface Testing:

1) Check with the spellings for all the labels
2) Check whether the Tab sequence is working properly in all the fields
3) Anyone option have to be selected as default in the Radio box
4) Able to select the options in the radio box by using right and left
arrows in the keyboard
5) Select option have to display as default in the combo box
6) It will not allow to enter a new option in the combo box
7) We can able to select the options in the list by using up and down
arrows in the keyboard
8) “ * “symbol have to display in all the mandatory fields
9) By clicking submit button without entering any texts, it have to
display error message in mandatory fields
10) By Clicking Cancel button it have to display the previous or home page
11) Font size should be proper as per the requirement
12) Font style should be proper as per the requirement
13) Spaces between the texts and the fields should be proper

If you know more about User Interface Testing, kindly write down in comments section or send an e-mail to me.

How to test a Text Box

2009-03-09T00:57:00.001-07:00

Listed below are the scenarios to test a text box in an application,

1) Check with the requirement whether it will accept numeric and special characters

2) Enter” HTML tag” and click save button
If it displays the entered texts means there is no defect.
If it converts the HTML tags and displays the message only means there is a defect

3) Enter “Java Script” and click save button
If it displays the entered texts means there is no defect.
If it converts the Script and displays the message only means there is a defect

4) Copy and paste a “Embed code” for a video from You Tube and click save button
If it displays the entered texts means there is no defect.
If it displays the video for that code means it is defect

5) Enter “Profile layout codes” and click save button
Ex : take code from http://www.pimpmyarea.com/getcode.php?style=archivos_css/movies2.css
If it displays the entered texts means there is no defect.
If it changes the design of the page means it is defect

6) Test With Boundary value conditions for the given character limitation
Ex: If it accepts 1 to 10 characters
Then Test with 0, 1,2,9,10,11
It will not accept 0 and 11 characters, if it accepts then there is an defect

7) Test by entering “Spaces” in the prefix and suffix of the entered character
It has to trim the spaces and have to display the texts properly

8) Test by entering “single quotes and double quotes”
It will result in Database error

9) Enter a text within Double quotes and click save button
Ex: “Testing”
Sometimes it will not show the entered text in the text box

10) Copy and Paste long texts from word or notepad
Ex: If the characters are limited between 1 to 10, then it will not allow to type text more than 10 characters, Some times copy texts from word document which have 15 characters and paste it in the text box, it will allow.

How to find broken links in a website

2009-03-03T05:50:00.000-08:00

If you are testing web based applications, then it is necessary to find the broken links in the website.

Links which is not redirected to proper pages or not showing any output page is known as broken links.

Listed below are the online tools to find broken links in your application

1) http://validator.w3.org/checklink
2) http://htmlhelp.com/tools/valet/

Other than these tools there is one tool called “Xenu” also used to find the broken links. But you have to install it in your local system. Here is the link to download “Xenu”

http://www.softpedia.com/get/Internet/Other-Internet-Related/Xenu-Link-Sleuth.shtml

These tools will not give you all the broken links in your website. Normally manual testing of a application is far better than testing with the help of tools.

If you know more about the tools to find broken links, kindly write down in comments section or send an e-mail to me.

What is “character set” and how to test “Character Set”:

2009-03-02T00:27:00.000-08:00

Character set: A defined list of characters recognized by the computer hardware and software. Each character is represented by a number.The ASCII character set, for example, uses the numbers 0 through 127 to represent all English characters as well as special control characters.

How to test Character set:

Scenario 1:

1) If you have admin rights for your web application, you can see an option for changing character set in main settings field. It will be normally displayed as “UTF-8”
2) Now Go to the site and change the UTF set in your browser via View--character encoding--more encoding--UTF-16
After choosing the UTF-16 check whether the texts in the site displayed properly or not?

Scenario 2:
1) Change the character set from UTF-8 into UTF-16 in admin and save changes
2) Now go to the site and change the UTF set and language to check whether site displays the texts properly or not.
To change language go to View--character encoding--Auto detect

Scenario 3:
1) After changing UTF character set in admin, check with the pop up’s and flash players in the site.
2) Sometimes change in UTF character set will results in pop up display and flash player display in the site (i.e.) pop up’s in the site and player will not display properly

Note: Test the above scenarios in all the major browsers.

If you know more about character set and testing of character set, kindly write down in comments section or send an e-mail to me.

Steps to clear cookies and caches in internet browsers

2009-02-25T22:14:00.000-08:00

In Our previous post we saw about the need to clear browser cookies and caches. In this post I will give you the steps to clear the cookies and caches for various internet browsers. These steps are only for windows operating system.

For Internet Explorer 6.0

1. On the Internet Explorer Tools menu, click Internet Options.
2. The Internet Options box should open to the General tab.
3. On the General tab, in the Temporary Internet Files section, click the Delete Files button.
4. From the same tab, select ‘Delete Cookies.’
5. Click “Close” and restart the browser.

For Internet Explorer 7.0

1. On the Internet Explorer Tools menu, click “Delete Browsing History.”
2. In the Temporary Internet Files section click on “Delete Files” and select “Yes.”
3. In the Cookies section click on “Delete Cookies” and select “Yes.”
4. Click “Close” and restart the browser.

For Safari

1. Open Safari.
2. Click Edit menu
3. Select Empty Cache.
4. Click Empty on the ‘Are you sure’ message box.
5. Exit and re launch the browser.
6. To delete your cookies, select preferences, then click on: Security tab->show cookies->remove all

For Opera

1. On the opera toolbar, click Tools and select “Preferences”
2. Choose “Advance” tab the “cookies” on the left side
3. Click “Manage Cookies”
4. And delete all the cookies
5. Exit and re launch browser

For Firefox

1) On the Firefox Tools menu, Click Clear private data
2) Select all the check boxes
3) Now click clear “Clear private data” button

If you know about the steps to clear browser cookies and caches in other operating systems, kindly write down in comments section.

Need of clearing cookies and caches

2009-02-23T06:11:00.000-08:00

Periodically we need to clear cookies and caches in our internet browsers and this will prevent hacking of your personal user name, password or some banking transaction details if you are using internet cafe or public computers for surfing
Reason for this is, application will store detail used in the application in browser cookies. And it can be able to hack by the hackers.
In testing it will use to find the updated files in the server. For example if you are testing an application and in a file and the next day developers are uploading new files into the server and giving it for testing. If you are going to test without clearing cookies and caches it will display the old files which is stored in the caches. In this place we need to clear the cookies and caches to view the updated files in the server.
So remember to delete cookies and clear caches whenever you are going to access internet or everyday before starting testing in your application.

I will give one example to view your user name and password of an application in internet browser cookie files. Mostly password will be in encrypted in all the sites, if not that will be one major security issue.
Open your application, in login field enter user name and password and enable the check box “Remember me” and click submit button.
After login go to tools---->internet option---->Settings in browsing history---->View files
Follow the above steps in IE7 browser to view the internet cookie files.

So follow this habit to clear cookies and caches often in your browser. In our next blog we can find the steps to clear the cookies and caches in various internet browsers.

Scenarios for Testing an "Upload" field

2009-02-19T01:38:00.000-08:00

1. Test uploading different types of image files (like .jpg, .png, .gif, .bmp, etc) and see if you could upload them.

2. Test uploading other files (like .exe, .dll, .mpg, .mov, .mp3, .wav, .rm, .doc etc) and see if It could break the uploading process.

3. Test with an image file with size other than the specified limit (the maximum allowed size was 500KB. So I had to try with 0 KB files, 1 MB image files, 5 MB files etc).

4. Try uploading a virus infected image file [You can use EICAR (European Institute of Computer Anti-virus Research) test files. These files are not actually viruses but behave as virus files] and see if the web server could detect the virus and stop the upload!

5. Test typing in a wrong path (like typing 'F:\ walpapers\aamir_khan_001.jpg', in place of a correct path 'F:\ wallpapers\aamir_khan_001.jpg'). Look at the wrong spelling of 'walpaper'). This can easily happen if a user is entering the path of the image file to be uploaded instead of browsing and selecting the image file. I had to see that the system was capable of detecting the wrong path name of the file.

6. Test cancelling an upload process and see what happens.

7. Test with a slower network speed and low system configuration.

8. Test While unplugging the internet connection while uploading.

9. Rename a images file with special characters and test by uploading it.

10. Test with corrupted image files (wrongly encrypted files).

11. Test by changing the file extension in browse field after selecting one image.
for Ex : Chnage jpeg into GIF

12. Test By closing the browser while uploading

Link for downloading virus affected files : http://www.eicar.org/anti_virus_test_file.htm

What is globalization and Localization Testing?

2009-02-16T22:49:00.001-08:00

Globalization Testing: This type of testing validates whether the application is capable for using all over the world and to check whether the input accepts all the language texts.

Localization Testing: This type of testing validates whether the application is capable for using in a particular location or in a particular country.

For Example, take a Zip code field in sign up form,

a) If the application is globalized then it will allow to enter alphanumeric inputs
b) If the application is localized (if it is INDIA) then it will allow to enter only numbers.

This is the purpose and use of globalization and localization testing.

Need of Globalization and Localization Testing:

2009-02-10T06:43:00.000-08:00

Today morning my manager came to my place and asked one clarification regarding one of our product that the product is multi language support or not?
We replied as “No, we are supporting multi language”.
Again he asked, whether a user can able to register as a new user by giving the details for registration in other languages except English.
We were not able to answer the question, because we didn’t try this scenario in our product. Then i opened my product sign up page and gave the username, first name, last name and about me fields in other languages.We shocked while submitting the form for registration. It displayed error message and user is unable to sign up if he/she gives the sign up details in other languages.We tried the same scenario with Google and it allowed to sign up. Then only we realized the importance of this globalization and localization testing. Then we concluded that if we give the inputs in any language, the applications have to work properly and it has to display the proper output.

Field that are to be tested for globalization and localization testing:

Sign Up page:

1. Username
2. First name
3. Last name
4. Phone number
5. Zip code
6. Entering answer for security question

Other pages:

1. Post comments page
2. Contact us
3. Shout outs
4. Blogs
5. Forums
6. Mail box
7. Profile page
8. Description fields in all the pages
9. Search field
10. Login field

Admin Section:

1. Site Settings page
2. Edit email templates page
3. Manage static pages
4. News letter
5. Member search
6. Report bugs
7. All the input text fields which is connected with database.

Important languages to be tested:

1. Arabic
2. French
3. Japanese
4. Chinese
5. Spanish
6. Russian

Steps to Download QTP 9.5 Demo version

2009-02-03T00:00:00.000-08:00

1. Go to this link : https://h10078.www1.hp.com/cda/hpdc/display/main/thanks.jsp?zn=bto&cp=54_4000_100__
2. Click products in the left side links
3. Upcoming page find "Hp Quick test professional" link under HP quality center
4. Click the link
5. Upcoming page click "HP 9.5 quick test evolution" link under Technical resources
6. Now it will ask for login/register
7. If you have account with HP just login and download the software
8. Otherwise Register and then download.

If you have any problems while executing the above steps, please drop a mail to prajeshbe@gmail.com

How to get Student id for HP exams ?

2009-02-02T02:29:00.000-08:00

Step 1 :

Go to the site http://www.hp.com/certification/ap/DrawerStatementBlackout.mht
Click "Asia Pacific" under "Regional partner portals"
Click "India"
Click "Register" in the upcoming page
Click "Yes" if you are going to apply for first time
Enter all the mandatory fields in the upcoming form and click "continue"
Upcoming page enter your company name and submit the form
A confirmation mail will comes to your mail id

Step 2 :

After three business days try to login using the registered details in http://h20375.www2.hp.com/portal/site/publicpartnerportal-ap/in/en/
After logging in click Train and certify link in the left panel
Click "Request Access"
Upcoming page choose the option "No" if you are a new to the exam
Click Agree the terms link
A pop up window will opens, and select yes in that page
Click Submit button.
Then again you have to wait for 3 more business days

Step 3 :

After that you can find links to get a student id
Under Quick link click "Access leaner id" link
Upcoming page click "My Profile"
There you can see your HP learner id in the top of the page.
It will start with "PL" and eight digit number
That it, this is your leaner id and now you are ready to take hp exam
Take a print out of that page and visit your nearest "NIIT" center
They will help you to take the exam.

Exam Fee for individual exam is Rs,2985

If you are not able to access after 3 more days or if you are having any trouble while applying you can leave a mail to premium.support@hp.com

If you have any queries in the above steps please drop a mail to prajeshbe@gmail.com

LOAD TESTING REQUIREMENTS

2009-01-31T19:33:00.000-08:00

1. Test data(User Name, Password etc)

2. Type of testing:

* Load Testing
* Stress Testing
* Endurance Testing

3. Specific time that when the scripts can be executed.

4. Architecture of the application

5. Load Generator

6. Server configuration

7. Expected Delay Time.

8. Expected Throughput time.

9. Exact bandwidth.

10. How many users going to access the application?

11. How many concurrent users?

12. What are the roles of the users?

13. Type of the application.

14. What are all the protocols using?

15. How many peak users?

16. What type of scenarios facing?

17. How often the peaks and when they are occurring?

Status in Loadrunner controller Scenario Groups

2009-01-31T19:23:00.000-08:00

Scenario Groups pane in the Run view of controller is to monitor the actions of all the Vusers and Vuser groups in the scenario.

The Status field of each Vuser group displays the current state of each Vuser in the group

1. Down Status: Vuser is down

2. Pending: Vuser is ready to be initialized and waiting for an available load generator

3. Init: The Vuser is being initialized on the remote machine.

4. Ready : The Vuser already performed the init section of the script and is ready to run.

5. Running: The Vuser is running. The Vuser script is being executed on a load generator

6. Rendezvous: The Vuser has arrived at the rendezvous and is waiting to be released by LoadRunner.

7. Done.Passed : The Vuser has finished running. The script passed.

8. Done.Failed : The Vuser has finished running. The script failed.

9. Error: A problem occurred with the Vuser

10. Gradual Exiting : The Vuser is completing the iteration or action it is running Before exiting.

11. Exiting : The Vuser has finished running or has been stopped, and is now exiting.

12. Stopped The Vuser stopped when the Stop command was invoked.

Available Protocols in Loadrunner 8.0

2009-01-31T19:21:00.001-08:00

1. Application Deployment Solution Protocol: Citrix protocol.

2. Client/Server Protocols : DB2 CLI, DNS, MS SQL, ODBC, Oracle (2-tier), Sybase Ctlib, Sybase Dblib, and Windows Sockets protocols.

3. Custom Protocols: C templates, Visual Basic templates, Java templates, Java script and VBscript type scripts

4. Distributed Components: For COM/DCOM, Corba-Java, and Rmi -Java

5. E-business protocols: For FTP, LDAP, Palm, Web (HTTP/HTML), Web Services, Dual Web/Winsocket protocols.

6. Enterprise Java Beans Protocols: EJB Testing and Rmi-Java protocols.

7. ERP/CRM protocols: For Baan, Oracle NCA, People soft-Tuxedo, People soft 8,

8. SAPGUI, SAP protocols -Web, and Siebel (Siebel-DB2CLI, Siebel-MSSQL, Siebel-Web, and Siebel-Oracle) protocols.

9. Legacy protocols: For Terminal Emulation (RTE).

10. Mailing Services protocols: Internet Messaging (IMAP), MS Exchange (MAPI),
POP3, and SMTP.

11. Middleware protocols: Jacada and Tuxedo (6, 7) protocols.

12. Streaming Protocols: For Media Player and RealPlayer protocols.

13. Wireless Protocols: For i-Mode, VoiceXML, and WAP protocols.

How to apply for CSTE exam

2009-01-30T23:13:00.000-08:00

Examinations in India, China, Sri Lanka and Brazil are administered every 2
months (6 times a year) at Software Certifications Sponsored Test locations
and are written examinations.
Registration Process

Step 1:Register on the 'Customer Portal' section on
www.softwarecertifications.org

Step 2:Apply for Candidacy once you are logged in. You will have to enter
your Personal Info, Education, References, etc. in order to satisfy the
Candidacy Prerequisite checks. The Candidacy Payment Wizard will take you
through the payment process.

Step 3: You can Schedule an Examination when you feel ready to actually take
the Examination.

In order to take the written examination at these locations, you need to
register 30 days before the selected examination date by filling the form in
the 'Customer Portal' section on www.softwarecertifications.org and making
the required payment.

The eligibility criteria is available on
http://www.softwarecertifications.org

Payment Details:
CSQA & CSTE:
Option 1: US$350
[Application Fee+ Study Guide]
Option 2: US$420
[Application Fee + Study Guide + hard copy of the Study Guide]
CSPM: US$400
[Application Fee]
Mode: The fee (in US$ only) can be paid by a dollar draft/check or by using
a credit card.

Examination Schedule:
Please visit the 'Examination schedule' section on
https://www.softwarecertifications.org/exams/schedule.htm for updates on
locations & dates.

Common Body of Knowledge [CBoK]: The Common Body of Knowledge (CBoK) is
listed on www.softwarecertifications.org & defines the scope of the
examination. The application fee includes access to the Guide to the Body of
Knowledge which will help you prepare for the examination.
QAI does not provide any sample/mock papers as the examination is meant to
test your hands on experience at work.Its an examination based Certification and we do not provide any kind of training to any candidate. However, for preparation you can:-

1. You can refer to study guide provided to you after the registration.
2. You can get a list of reference books on www.softwarecertifications.org.
3. You can join some online forums like Yahoo, etc.
4. You can get in touch with people who are already certified (personally/online) for internal sessions.

To view the exam schedule, eligibility criteria, to apply for the
examination and for more information on these certifications, please visit
www.softwarecertifications.org

Steps to apply for ISTQB exams

2009-01-30T22:56:00.000-08:00

Go to the site http://208.116.30.129/

Click "Exam Dates", there you can find the exam dates for various cities across india.

Check the examination schedule for your city.

Fill the Online Enrollment Form.A link for Enrollment form will be given in that same page

You would immediately receive a confirmation mail in your Personal ID along with further instructions.

As per instructions Send a D/D of amount specified in mail in favour of INDIAN TESTING BOARD, payable at 'NOIDA' to their Noida Office

Address to send DD is INDIAN TESTING BOARD
A-24, First Floor, Sector-59
NOIDA - 201301(U.P)

Then after one week they will send a payment confirmation mail

You will be informed of the timing and procedure of the examination. Appear for the examination on the designated date, time and venue.

Please do not forget to bring a photo identity (Passport, Driving License, Election Card etc.) with you when you appear for the examination.

You will be informed of your result within two weeks and passing candidates will receive the certificate within eight weeks.

If any enquiry related ISTQB and Sample question dumps and syllabus please contect me at prajeshbe@gmail.com

Upcoming Schedule for ISTQB

2009-01-30T22:47:00.000-08:00

Examination Schedule for Foundation Level

City

Date/Month/Time

Venue

Ahmedabad

31th Jan	2009
31th Mar	2009

Tops Technologies

Pin: 380009
Contact No: 01204355270
Contact Person: Sonal Garg

Bangalore

15th Feb	2009
29th Mar	2009
17th May	2009
28th June	2009
16th Aug	2009
27th Sep	2009
15th Nov	2009
20th Dec	2009

St. Joseph's Pre-University College
Opp. Good Shepherd Auditorium, Residency Road, Field Marshal Cariappa Road, Bangalore
Pin: 560025
Contact No: 09343494617
Contact Person: Mr. Pravesh Pugalia
Email: pravesh@indiantestingboard.com

Chennai

15th Feb	2009
29th Mar	2009
17th May	2009
28th June	2009
16th Aug	2009
27th Sep	2009
15th Nov	2009
20th Dec	2009

Meenakshi College For Women
363, Arcot Road, Kodambakkam, Chennai
Pin: 600024
Contact No: 09343494617
Contact Person: Mr. Pravesh Pugalia
Email: pravesh@indiantestingboard.com

Cochin

22th Feb	2009
05th April	2009
21th June	2009
02nd Aug	2009
18th Oct	2009
29th Nov	2009

St. Albert's College
Banarji Road, Cochin
Pin: 682018
Contact No: 0120-4236187
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Coimbatore

24th May	2009
30th Sep	2009

Mazenet
Maze Net Solution (P) Ltd., 12e,1st Floor,10th Street, Padmalaya Towers , Coimbatore - 12.
Contact No: 01204236187
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Coimbatore

21th Mar	2009
26th July	2009
22th Nov	2009

IIST
734, President Hall G.D.Naidu Charities Building, Avinashi Road, Coimbatore - 641018
Contact No: 01204236187
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Hyderabad

15th Feb	2009
29th Mar	2009
17th May	2009
28th June	2009
16th Aug	2009
27th Sep	2009
15th Nov	2009
20th Dec	2009

Mind Q
Mind Q Systems Pvt Ltd, 8-3-214/7, Srinivasa Nagar Colony (W), S.R.Nagar, Hyderabad
Pin: 500038
Contact No: 0120-4236187
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Indore

22th Feb	2009
26th April	2009

SQTL
SQTL Integrated Solutions Pvt Ltd. 308, Akashdeep Complex 21, Sneh Nagar, Sapna-Sangeeta Main Road, Indore
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Kolkata

15th Feb	2009
29th Mar	2009
17th May	2009
28th June	2009
16th Aug	2009
27th Sep	2009
15th Nov	2009
20th Dec	2009

Vallabhram Mehta Boys Secondary School
6 Pollock Street, Kolkata-700001
Pin: 700001
Contact No: 0120-4355270
Contact Person: Miss Sonal Garg
Email: sonal@indiantesitngboard.com

Madurai

16th April	2009
21th Aug	2009
27th Nov	2009

Tandem Infotech Pvt .Ltd
Opp.Ambiga Theatre, Anna Nagar, Madurai
Pin: 625020
Contact No: 0120-4355270
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Mumbai

15th Feb	2009
29th Mar	2009
17th May	2009
28th June	2009
16th Aug	2009
27th Sep	2009
15th Nov	2009
20th Dec	2009

Cosmopolitan’s Valia College of Commerce
Near Versova Police Station D N Nagar, Cosmopolitian Education Society Road, Andheri(West) Mumbai
Pin: 400053
Contact No: 0120-4236187
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Nagpur

31th Mar	2009
08th June	2009
18th Aug	2009
17th Nov	2009

Vise India
Vise India 1st Floor, Dhanwantaree Hospital, Khare Town, Dharampeth, Nagpur - 440 010
Pin: 440 010
Contact No: 01204236187
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Noida

15th Feb	2009
29th Mar	2009
17th May	2009
28th June	2009
16th Aug	2009
27th Sep	2009
15th Nov	2009
20th Dec	2009

Indian Testing Board
A-24, First Floor Sector-59 Noida
Pin: 201301
Contact No: 0120-4236187
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Pune

15th Feb	2009
29th Mar	2009
17th May	2009
28th June	2009
16th Aug	2009
27th Sep	2009
15th Nov	2009
20th Dec	2009

Nowrosjee Wadia College
19, Late Principal V K Joag Path, Pune
Pin: 411001
Contact No: 0120-4355270
Contact Person: Mr. Mohnesh Bakshi
Email: mohnesh@indiantestingboard.com

Tirunelveli

28th May	2009
25th Sep	2009
18th Dec	2009

TANDEM
TANDEM 124,Trivandrum Road, Opp.Siddha College(Next to IOB) Palayamkottai Tirunelveli
Pin: 627 002
Contact No: 0120-4355270
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Trivandrum

15th Feb	2009
29th Mar	2009
17th May	2009
28th June	2009
16th Aug	2009
27th Sep	2009
15th Nov	2009
20th Dec	2009

TIME Shiv Bhavan
Opp SBI,Kannamoola, Medical College P.O., Trivandrum
Pin: 695 011
Contact No: 0120-4236187
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Advanced Level

City

Date/Month/Time

Venue

Ahmedabad

31th Jan	2009
31th Mar	2009

Technical Tester
Functional Tester
Test Manager

Tops Technologies

Pin: 380009
Contact No: 01204355270
Contact Person: Sonal Garg

Bangalore

15th Feb	2009
17th May	2009
16th Aug	2009
15th Nov	2009

Technical Tester
Functional Tester
Test Manager

St. Joseph's Pre-University College
Opp. Good Shepherd Auditorium, Residency Road, Field Marshal Cariappa Road, Bangalore
Pin: 560025
Contact No: 09343494617
Contact Person: Mr. Pravesh Pugalia
Email: pravesh@indiantestingboard.com

Chennai

15th Feb	2009
17th May	2009
16th Aug	2009
15th Nov	2009

Technical Tester
Functional Tester
Test Manager

Meenakshi College For Women
363, Arcot Road, Kodambakkam, Chennai
Pin: 600024
Contact No: 09343494617
Contact Person: Mr. Pravesh Pugalia
Email: pravesh@indiantestingboard.com

Cochin

22th Feb	2009
05th April	2009
21th June	2009
02nd Aug	2009
18th Oct	2009
29th Nov	2009

10.00-11.30 AM Technical Tester
11.45-1.15 PM Functional Tester
2.00-3.30 PM Test Manager

St. Albert's College
Banarji Road, Cochin
Pin: 682018
Contact No: 0120-4236187
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Coimbatore

24th May	2009
30th Sep	2009

10.00-11.30 AM Technical Tester
11.45-1.15 PM Functional Tester
2.00-3.30 PM Test Manager

Mazenet
Maze Net Solution (P) Ltd., 12e,1st Floor,10th Street, Padmalaya Towers , Coimbatore - 12.
Contact No: 01204236187
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Coimbatore

21th Mar	2009
26th July	2009
22th Nov	2009

10.00-11.30 AM Technical Tester
11.45-1.15 PM Functional Tester
2.00-3.30 PM Test Manager

IIST
734, President Hall G.D.Naidu Charities Building, Avinashi Road, Coimbatore - 641018
Contact No: 01204236187
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Hyderabad

15th Feb	2009
17th May	2009
16th Aug	2009
15th Nov	2009

Technical Tester
Functional Tester
Test Manager

Mind Q
Mind Q Systems Pvt Ltd, 8-3-214/7, Srinivasa Nagar Colony (W), S.R.Nagar, Hyderabad
Pin: 500038
Contact No: 0120-4236187
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Indore

22th Feb	2009
26th April	2009

10.00-11.30 AM Technical Tester
11.45-1.15 PM Functional Tester
2.00-3.30 PM Test Manager

SQTL
SQTL Integrated Solutions Pvt Ltd. 308, Akashdeep Complex 21, Sneh Nagar, Sapna-Sangeeta Main Road, Indore
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Kolkata

15th Feb	2009
17th May	2009
16th Aug	2009
15th Nov	2009

Technical Tester
Functional Tester
Test Manager

Vallabhram Mehta Boys Secondary School
6 Pollock Street, Kolkata-700001
Pin: 700001
Contact No: 0120-4355270
Contact Person: Miss Sonal Garg
Email: sonal@indiantesitngboard.com

Madurai

16th April	2009
21th Aug	2009
27th Nov	2009

10.00-11.30 AM Technical Tester
11.45-1.15 PM Functional Tester
2.00-3.30 PM Test Manager

Tandem Infotech Pvt .Ltd
Opp.Ambiga Theatre, Anna Nagar, Madurai
Pin: 625020
Contact No: 0120-4355270
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Mumbai

15th Feb	2009
17th May	2009
16th Aug	2009
15th Nov	2009

Technical Tester
Functional Tester
Test Manager

Cosmopolitan’s Valia College of Commerce
Near Versova Police Station D N Nagar, Cosmopolitian Education Society Road, Andheri(West) Mumbai
Pin: 400053
Contact No: 0120-4236187
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Nagpur

31th Mar	2009
08th June	2009
18th Aug	2009
17th Nov	2009

10.00-11.30 AM Technical Tester
11.45-1.15 PM Functional Tester
2.00-3.30 PM Test Manager

Vise India
Vise India 1st Floor, Dhanwantaree Hospital, Khare Town, Dharampeth, Nagpur - 440 010
Pin: 440 010
Contact No: 01204236187
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Noida

15th Feb	2009
17th May	2009
16th Aug	2009
15th Nov	2009

Technical Tester
Functional Tester
Test Manager

Indian Testing Board
A-24, First Floor Sector-59 Noida
Pin: 201301
Contact No: 0120-4236187
Contact Person: Miss Sonal Garg
Email: sonal@indiantestingboard.com

Pune

15th Feb	2009
17th May	2009
16th Aug	2009
15th Nov	2009

Technical Tester
Functional Tester
Test Manager

Nowrosjee Wadia College
19, Late Principal V K Joag Path, Pune
Pin: 411001
Contact No: 0120-4355270
Contact Person: Mr. Mohnesh Bakshi
Email: mohnesh@indiantestingboard.com

Tirunelveli

28th May	2009
25th Sep	2009
18th Dec	2009

10.00-11.30 AM Technical Tester
11.45-1.15 PM Functional Tester
2.00-3.30 PM Test Manager

TANDEM
TANDEM 124,Trivandrum Road, Opp.Siddha College(Next to IOB) Palayamkottai Tirunelveli
Pin: 627 002
Contact No: 0120-4355270
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Trivandrum

15th Feb	2009
17th May	2009
16th Aug	2009
15th Nov	2009

Technical Tester
Functional Tester
Test Manager

TIME Shiv Bhavan
Opp SBI,Kannamoola, Medical College P.O., Trivandrum
Pin: 695 011
Contact No: 0120-4236187
Contact Person: Sonal Garg
Email: sonal@indiantestingboard.com

Experience while writing the ISTQB certification

2009-01-30T22:44:00.000-08:00

We planned to write our ISTQB certification as a team.

Gathered the ISTQB materials from the website http://www.istqb.org/download.htm

Also the sample questions from the various groups, communities and forums.

Each one read the material from starting to end and understood the meaning of each and every word given in the material. Then we had a discussion at least for one hour a day where we shared concept each of us understood .At last we will derive at the best answers for each concept .

Then we practiced our self by writing the sample test in the questions we collected from various sources.

Request for those writing the ISTQB examination

1.Read the ISTQB material thoroughly.

2.Workout with the sample papers by collecting through various groups, communities and forums.

3. Understand the concept clearly .

“TEAM WORK WINS”—IF YOUR TEAM IS MUTUAL THEN THE WORLD WILL BE ON YOUR FINGER TIPS

I am sure that if you follow this you will be an ISTQB certifier

Fundamentals of testing

2009-01-30T22:42:00.000-08:00

We need to understand, explain, give reasons, compare, classify, categorize, give examples and summarize;

Terms we need to understand in this Chapter are

1. Bug
2. Defect
3. Error
4. Failure
5. Fault
6. Mistake
7. Quality
8. Risk.

Error:

·Mistake made by the human beings

·An error or defect in software or Hardware that causes a program to malfunction

Defect :

* Due to mistake it produces a fault or bug in the code software or a system, or in a document.
* A defect is any variance between actual and expected results.

Failure :

* If a defect in code is executed, the system will fail to do
* what it should do or do something it shouldn’t

So the relation is

Error =>Defect=>Failure

Defect :

* Problem in algorithm leads to failure
* Non conformance to requirements or functional / program specification

Bug:

* Deviation from the expected result.
* It is a fault in a program which causes the program to perform in an unintended or unanticipated manner

Causes for Defects:

Defects occur because human beings are fallible and because there is

* time pressure,
* complex code,
* complexity of infrastructure,
* changed technologies, and/or many system interactions.

Causes for Failures

Failures can be caused by

* environmental conditions as well: radiation, magnetism, electronic fields,
* pollution can cause faults in firmware or influence the execution of software by changing
* hardware conditions.

Purpose of testing :

* Reduce the risk
* Contribute to the quality of the software system
* Could give confidence in the quality of the software if it finds few or no defects

Quality assurance :

Lesson Learnt from the previous projects and by understanding the root cause of defects found in other projects, processes can be improved, which in turn should prevent those defects from

Reoccurring and, as a consequence, improve the quality of future systems.

What is Risk?

Uncertainty — An event may occur or may not occur

Why is Risk arises?

• Uncertainty

• Inexperience

• Inability to accurately forecast

How much testing is enough?

* Level of risk, including technical and business product and project risks,

* Project constraints such as time and budget

Principles of testing

2009-01-30T22:39:00.000-08:00

A number of testing principles have been suggested over the past 40 years and offer general

guidelines common for all testing.

Principle 1 – Testing shows presence of defects

Testing can show that defects are present, but cannot prove that there are no defects.

Testing reduces the probability of undiscovered defects remaining in the software but, even if no defects are found, it is not a proof of correctness.

Principle 2 – Exhaustive testing is impossible

Testing everything (all combination of inputs and preconditions) is not feasible except for trivial

cases.

Principle 3 – Early testing

Testing activities should start as early as possible in the software or system development life cycle,

and should be focused on defined objectives

Principle 4 – Defect clustering

A small number of modules contain most of the defects discovered during pre-release testing, or

are responsible for the most operational failures.

Principle 5 – Pesticide paradox

If the same tests are repeated over and over again, eventually the same set of test cases will no

longer find any new defects. To overcome this “pesticide paradox”, the test cases need to be

regularly reviewed and revised, and new and different tests need to be written to exercise different

parts of the software or system to potentially find more defects.

Principle 6 – Testing is context dependent

Testing is done differently in different contexts. For example, safety-critical software is tested

differently from an e-commerce site.

Principle 7 – Absence-of-errors fallacy

Finding and fixing defects does not help if the system built is unusable and does not fulfill the users’

Software Testing Types

2009-01-30T22:34:00.000-08:00

* COMPATIBILITY TESTING. Testing to ensure compatibility of an application or Web site with different browsers, OS, and hardware platforms. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite.

* FUNCTIONAL TESTING. Validating an application or Web site conforms to its specifications and correctly performs all its required functions. This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product’s user interface, APIs, database management, security, installation, networking, etc testing can be performed on an automated or manual basis using black box or white box methodologies.

* LOAD TESTING. Load testing is a generic term covering Performance Testing and Stress Testing.

* PERFORMANCE TESTING. Performance testing can be applied to understand your application or WWW site’s scalability, or to benchmark the performance in an environment of third party products such as servers and middle ware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions.

* REGRESSION TESTING. Similar in scope to a functional test, a regression test allows a consistent, repeatable validation of each new release of a product or Web site. Such testing ensures reported product defects have been corrected for each new release and that no new quality problems were introduced in the maintenance process. Though regression testing can be performed manually an automated test suite is often used to reduce the time and resources needed to perform the required testing.

* SMOKE TESTING. A quick-and-dirty test that the major functions of a piece of software work without bothering with finer details. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

* STRESS TESTING. Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. A graceful degradation under load leading to non-catastrophic failure is the desired result. Often Stress Testing is performed using the same process as Performance Testing but employing a very high level of simulated load.

* UNIT TESTING. Functional and reliability testing in an Engineering environment. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration.

Difference between Client/ Server testing and web based testing

2009-01-30T20:28:00.000-08:00

Projects are broadly divided into two types of :

· 2 tier applications

· 3 tier applications

CLIENT / SERVER TESTING
[a] This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having front end and back end.

The application launched on front end will be having forms and reports which will be monitoring and manipulating data

Eg : applications developed in VB,VC++,Core Java,C,C++,D2K,Power Builder etc.,
The back end for these applications would be MS Access, SQL Server, oracle, sybase, mysql, quadbase

The tests performed on these type of applications would be
- user interface testing
- manual support testing
- Functionality testing
- compatibility testing & configuration testing
- inter systems testing

WEB TESTING
[b] This is done for 3 tier applications (developed for Internet / intranet / xtranet)

Here we will be having Browser, web server and DB server.

The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc.,
(we can monitor through these applications)

Applications for the web server would be developed in Adv Java, ASP, JSP, VB Script, JavaScript, Perl, Cold Fusion, PHP etc.,
(all the manipulations are done on the web server with the help of these programs developed)

The DB server would be having oracle, sql server, sybase, mysql etc.,
(all data is stored in the database available on the DB server)

The tests performed on these type of applications would be
- user interface testing
- Functionality testing
- security testing
- browser compatibility testing
- load / stress testing
- interoperability testing/inter systems testing
- storage and data volume testing

What we will do in Manual Testing?

2009-01-30T20:26:00.000-08:00

1. Understand the functionality of program
2. Prepare a test environment
3. Execute test case(s) manually
4. Verify the actual result
5. Record the result as Pass or Fail
6. Make a summary report of the Pass and Fail test cases
7. Publish the report
8. Record any new defects uncovered during the test case execution

Flow of testing

2009-01-30T20:21:00.000-08:00

Before testing any application we should follow some standard flow.
Generic Testing flow is as follows

1. Smoke Testing
2. Sanity Testing
3. Component testing
4. Integration testing
5. System testing
6. Acceptance testing

Smoke testing is originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke... We will be concentrating on Basic functionality of the product. It is also called as Build verification testing

In Sanity Testing we will be focusing on the major functionality or the functionality in detail. It is the subset of Regression testing

In Component Testing we will be testing module by module

In Integration testing one or more modules are combined and tested. Eg: In larger domains like Telecom, there will be many modules so we will be integrating the modules and will be testing

In System testing all the modules are combined and the whole application is tested

Acceptance testing will be done to ensure the confidence in the system and it is done mainly by the end users

Note:

The flow of testing varies depending on the organization

Basics of Software Testing

2009-01-30T20:17:00.000-08:00

“Testing is a skill. While this may come as a surprise to some people, it is a simple fact”

Software Testing:

Software testing is the process of finding the defects as soon as possible and fixing them before delivering products to the client and also verify that the application meets the client’s requirement.
This increases the “Quality” of the product and decreases the “Risk”

Importance of Testing:

It Increases Customer satisfaction and the number of customers as well.
It Increases the Quality of the application.
It Increases the reputation of the organization.

Methods of Testing:

1) Manual Testing
2) Automation Testing

Levels of Testing:

1) Unit testing
2) Integration testing
3) System Testing
4) Acceptance testing

Types of Testing: (For Web Applications)

Unit Testing:

Done by Developers.

Functional Testing:

1) Sanity Testing
2) Smoke Testing
3) Component Testing
4) Integration Testing
5) Regression Testing
6) URL Testing
7) System Testing
8) Globalization and Localization Testing

Non-Functional Testing:

1) Load Testing
2) Performance Testing
3) Compatibility Testing
4) Installation Testing
5) Usability Testing
6) User Interface Testing
7) Security Testing

Inroduction

2009-01-30T20:12:00.000-08:00

I proudly present this blog to the members who are new to software testing field
and the people who are having eager to know the concept, process and definitions of testing clearly.
I have 4 years of experience in software testing and also got ISTQB and Expert Rating certification.I have participated in so many blogs as a member for the past three years and now i have started my own blog in software testing field.

The posts in this site are based upon my real-time experiences.
please email me to prajeshbe@gmail.com,if you have any doubts

Moderator,
softwaretestingwinners.blogspot.com