Wednesday, July 31, 2013

Neo Load

Steps for doing Load Testing with NeoLoad:

1. Recording HTTP traffic between browser and server
NeoLoad includes a proxy server that records all server requests and responses.
2. Defining test parameters
Defining Virtual User behavior and setting scenario parameters such as load policy (constant, ramp-up, peak or custom) or the number of Virtual Users to be simulated in the test.
Setting performance monitors (CPU, memory, disk usage, and so on) for your servers.
3 .Running the test
Monitoring the ongoing test with the aid of real-time graphs and stats.
4. Analyzing the results
Obtaining a summary of the test and then examining its details using the graphs and statistical tables.

Designing a Test Scenario:

Designing a test scenario consists in recording a web browsing sequence. NeoLoad keeps track of every browsing action to create a simulated user: It is the Virtual User. The Virtual User helps generate a behavior pattern, called Virtual User Profile. When running a test, NeoLoad relies on the Virtual User Profile to create duplicates — customized with variables — of the simulated user.

A test scenario is easy and quick to design, within a test project, thanks to the wizards available in NeoLoad. The design process includes the following steps:

-> Creating a test project with the File > New command in the NeoLoad Controller



-> Creating a Virtual User and configuring the recording conditions from the Welcome wizard or with the Record > Start Recording command



-> Recording the sequence in the browser and organizing actions in Containers while recording



-> Once recording is done, setting post-recording parameters



-> Configuring the Virtual User Profile in the Vitual Users tab of the Design section in the NeoLoad Controller



-> Checking the Virtual User Profile in the Check Virtual User wizard, accessible with Run > Start checking in the NeoLoad Controller



-> Organizing Profiles in groups — called Virtual Users Populations — in the Populations tab of the Design section in the NeoLoad Controller



-> Defining the monitors of the servers hosting the tested application, in the Monitors tab of the Design section in the NeoLoad Controller



 To design a test scenario:
1. In NeoLoad, choose File > New to create a new test project.
2. In the project, click Start Recording. In the Recording dialog box, enter the name of the Virtual User and specify the conditions of the browsing sequence you are ab out to capture.
3.In the displayed web browser, enter the URL of the test site. Browse as usual. NeoLoad records all your actions.
4. When recording (or after), you can create Containers to organize the visited pages and structure your scenario as business transactions. Subsequently you can configure them for reuse in other scenarios.
5. Once you are done with the browsing sequence, click Stop Recording. The Post-recording Wizard pops up. Follow the wizard steps to configure your Virtual User.
6. Back in the NeoLoad Controller, specify the running parameters of the new Virtual User in the Runtime Parameters area.
7. To check the Virtual User — and correct errors or unexpected behavior —, choose Run > Start Checking > Start Checking. Check the requests and the responses. Check every potential error raised by NeoLoad.
8. Back in the NeoLoad Controller, you choose the Populations tab to manager Virtual Users groups with the wizard.
9. Choose the Monitors tab to define the monitors of the servers hosting the tested application.

Running a Test:
Running a test consists in replaying a recorded scenario, but with amplified parameters of load and length. A test plan can meet a number of complementary objectives: checking the application in a unitary test, launching a realistic test on the application, and testing the application to its limits. Inspecting the results of every test helps take the necessary actions to ensure the application is robust and productive enough. For more information, see Defining Objectives.
In the Runtime section of the NeoLoad Controller, the test running process must be defined before launching it:
-> Configuring the test parameters and starting the test in the Scenarios tab in the NeoLoad Controller



Once started, the test can be followed in real time with a variety of information tabs:
-> Following the general process of the test in real time in the Runtime Overview tab



To run a test:
1. In the NeoLoad Controller, open your project. Click Runtime.
2. In the Scenarios tab, choose a scenario and a Population for the test. Specify the test parameters (length, load, number of Virtual Users, and so on).
3. To launch the test, choose Run > Start playing. Enter the name and description of your test. Click OK.
4. In the Runtime Overview tab, watch the general performance of the test.
5. In the Runtime Graphs tab, select the graphs of specific interest with drag-and-drops.
6. In the Runtime Errors tab, select a raised running error to view its description.
7. In the Runtime Alerts tab, select a raised server or SLA alert to view its description.
8. In the Runtime Users tab, watch the Virtual Users used in the test.
9. At the end of the end, NeoLoad automatically display the Results section.

Note: All the above information is copied from the following webs site. please visit the site for details information.

Different Tools

This Post contains information about the versions of all the below mentioned Tools.

Document Management Tool:

Version Controlling Tool:

Defect Management Tool:

Functional Testing Tool:

Performance/Load Testing Tool:

Open Source Tool:



Defect Management Tool: QC

3. QC

QC: Quality Center is just not a defect management tool. It is a Test management tool which sue for managing all test related activities like, Creating retirement, test cases, tracking bug e.t.c.

Quality Center Version History
1) 8.0 - First Version QC
2) 8.2 - SP1
3) 9.0 - In 2006
4) 9.2 - In 2007
5) 9.5 - In 2008
6) 10.0 - In 2009

7) 11.0 - In 2010

Developer(s) HP/Mercury Interactive
Stable release 11.5
Development status Active
Operating system Microsoft Windows or UNIX
Type quality management/test management
License Proprietary
Website HP Quality Center

Defect Management Tool: Jira


Jira: Jira is a bug tracking tool this is also use for requirement management.

Release Versions: 

JIRA 1:released in 2002[1]

JIRA 2:released in 2003[9]

JIRA 3:3.0, released 12 October 2004[10]
3.13, released 9 September 2008[11]

JIRA 4:4.0, released 6 October 2009[12]
4.1, released 7 April 2010
4.2, released 21 October 2010[13]
4.3, released 16 March 2011[14]
4.4, released 2 August 2011[15]

JIRA 5:5.0, released 22 February 2012[17]
5.1, released 9 July 2012[18]
5.2, release 11 November 2012[19]

JIRA 6:6.0, released 21 May 2013[20]

Developer(s): Atlassian, Inc.
Language: This is Written in Java
Operating system:  Platform-independent
Type: This is Bug tracking system, project management software
This is  License tool, free for use by official non-profit organizations, charities, and open-source projects, but not religious organizations
Website atlassian.com/software/jira


Version Controlling Tool: VSS

2. Subversion:

VSS: Visual SourceSafe is a version control system which is used for maintaining the version of the code and the test script and other documents. This  is from Microsoft.

Developer(s) Microsoft
Initial release 1994
Stable release 2005 (8.0.50727.42) / October 2005
Operating system Windows
Type Revision control
License Proprietary commercial software

Version Controlling Tool: Subversion



Subversion:  Subversion is a software versioning control system. It is open source tools.

Release History:

There were many releases Pre-1.0 releases that included a change in the filesystem database schema (and therefore required a repository reload). There will be no more such releases before Subversion 2.0.

Current Release: Subversion 1.0







Defect Management Tool: Bugzilla


Bugzilla: Bugzilla is bug tracking tool. It is Web based tool. It is an open source tool.

Version Numbers: Bugzilla version numbers will be in the form of aa.bb or aa.bb.cc.
 Stable release versions of Bugzilla will have an even number for bb. Any number in cc, if present, will indicate a bug-fix (and/or security fix) update to the stable version.
 Development versions always have an odd number for bb. Development versions are released periodically, and cc only indicates the passage of time since the previous version (how much time is up for debate).

Stable Release:  Bugzilla 4.4 is our current stable release

Current Stable Release Date: 4.4 May 22, 2013

Functional Testing Tool: QTP


QTP: HP Quick Test Professional is use for doing functional and regression testing for web based and desktop based applications.

Language: It uses VB script language for writing your scripts.

Current Version is : 11.5

Versions Release date: 

11.5 - Released in 2012
11.0 - Released in 2010
10.0 - Released in 2009
9.5 - Released in 2008
9.2 - Released in 2007
9.1 - Released in 2007
9.0 - Released in 2006
8.2 - Released in 2005
8.0 - Released in 2004
7.0 - Never released.
6.5 - Released in 2003
6.0 - Released in 2002
5.5 - First release. Released in 2001

Functional Testing Tool: Selenium


Selenium:  Selenium is a suite of tools to automate web browsers across many platforms. Selenium runs in many browsers and operating systems it  can be controlled by many programming languages.

Selenium IDE: Selenium IDE is a Firefox add-on that makes it easy to record and playback tests in Firefox 2+. You can even use it to generate code to run the tests with Selenium Remote Control.

latest released version 2.2.0

Selenium Remote Control: Selenium Remote Control  is a client/server system that allows you to control web browsers locally or on other computers, using almost any programming language and testing framework.
Download version 2.33.0

Selenium WebDriver: Selenium WebDriver can drive a browser natively either locally or on remote machines.

Selenium Grid: Selenium Grid takes Selenium Remote Control to another level by running tests on many servers at the same time, cutting down on the time it takes to test multiple browsers or operating systems.
Note: Above information is copied from this site http://docs.seleniumhq.org/docs/

Performance/Load Testing Tool: Silk Performer


Silk Performer: Silk Performer is a software performance testing tool. It was originally developed by Segue Software which was acquired by Borland in 2006. Borland was acquired by Micro Focus International in 2009.
Current Version  :9.5

Note: --SilkPerformer 6.5 needs a SilkPerformer 6.5 license and cannot be used with a SilkPerformer 6.0 license, however your SilkPerformer 6.5 license will allow use of older versions.

Performance/Load Testing Tool: Neo Load

2. Neo Load

Neo Load:  NeoLoad  is a Load and Stress testing tool use for web base applications. This is also used for doing  load and stress testing for web services.

Versions:
The current version of NeoLoad is 4.1.3. NeoLoad 4.1 (4.1.3 - latest version)

Version Release date:
1.0 March 1, 2005 -
1.1 July 26, 2005 -
2.0 July 27, 2006 SOAP / Linux & Solaris platforms monitor / SNMP monitor / Apache monitor / WebLogic monitor / Websphere monitor
2.1 February 13, 2007 Apache Tomcat monitor / Oracle database monitor
2.2 July 17, 2007 AIX monitor / HP-UX monitor / JBoss monitor / MySQL monitor
2.3 December 3, 2007 OAS monitor / JOnAS monitor / DB2 database monitor / PostgreSQL database monitor
2.4 March 28, 2008 Adobe Flex / Oracle Forms / IIS monitor / SQL Server monitor / .Net monitor
2.4.2 May 19, 2008 Refactor of Telnet/SSH module in two modules Linux and Solaris.
2.4.4 July 3, 2008 dynaTrace
3.0 May 15, 2009 GWT
3.0.6 October 15, 2009 GlassFish / SAP / Adobe LCDS
3.1 June 8, 2010 Push / RTMP / Java Serialization
3.1.3 October 26, 2010 CA APM
3.2.0 February 23, 2011 Cloud / Siebel / Silverlight / VMware monitor
4.0.0 April 4, 2012 Collaboration / JMX monitor
4.1.0 November 21, 2012 Monitoring Data Import module

Developer(s):  Neotys
Lanaguage: This Tool id written in Java
Operating system: Microsoft Windows, Linux, Solaris
Available in:  English, French
This is a licensed tool.
Website www.neotys.com


Friday, July 26, 2013

Selenium IDE

Selenium IDE Version Issue

[error] Unexpected Exception: fileName -> chrome://selenium-ide/content/selenium-core/scripts/htmlutils.js, lineNumber -> 309, columnNumber -> 8 

Are you getting this kind of error in Selenium IDE ?

Just upgrade your Selenium IDE to version 2.2 and your script will run smoothly.

I was getting this error and the reason was i was having Firefox version 22 and old selenium version does not support this version of Firefox. So if you firexfox version 22 then just upgrade IDE.

How to?

1.     Open the selenium site: http://docs.seleniumhq.org/
2.     Click on download
3.     Download selenium IDE
4.     Click on download


5.     Click on allow


   6.      You will see the below screen


7. Click on Install


8. It’s done restart your Firefox, Record you script and it will work.




Tuesday, July 2, 2013

Document Management Tool: Confluence

Confluence

Confluence:   Confluence is an open source tool which is used for managing documents. This tool we can also use for writing Project Plan, Test Plan or other Test Related documents.
Confluence is also known as team collaboration software. It is written in java.



Version of this Tool: 
Atlassian Confluence
Developer(s) : Atlassian
Initial release:  25 March 2004


Stable release 5.1 / March 24, 2013.