Explain FuncUnit and QUnit - Web Functional/Regression Test Tool

FuncUnit and QUnit are both tools developed for web functional and regression testing. In this article we first discuss about the FuncUnit testing tool.

About FuncUnit Tool

- It is an open source framework and therefore free to use. 

- The API that this tool uses is based up on the JQuery.

- FuncUnit can either be used as a standalone application or a part of the JavaScript full stack framework. 

- This JavaScript framework is commonly known as the JavaScript MVC. 

- Almost all the modern browsers are supported by FuncUnit on almost all the platforms such as mac, linux etc.

- The tool also offers you a choice of running the tests through selenium. 

- An integrated development environment or IDE called funcIT is also available for this tool. 

- Another component is there using which synthetic events can be created and default event behavior can be performed.

- It is known as the Syn and it can simulate events such as dragging the mouse, clicking, typing and so on. 

- Using syn complex JavaScript functional testing can also be carried out. 

- FuncIT lets you do the testing directly in the browser. 

- Writing, running and debugging of the tests takes place in the web browsers. - FuncUnit makes this all so easy. 

- You just need to open a page and start the debugger. 

- FuncUnit uses syntax similar to that of the JQuery. 

- This is the perfect web testing tool for you if like short and flexible test cases.  - You can run the tests in any of the browsers and later automate them via selenium. 

- FuncUnit supports the following versions of the modern browsers:

1. Internet explorer version 6 and above.
2. Firefox version 2 and above.
3. Safari version 4 and above.
4. Chrome
5. Opera version 9 and above.

- Platforms supported are mac, PC and Linux. 

- In other words you have a complete automated testing suite.

- Some of the features are:

1.   Functional testing

2.   High fidelity

3.   Automated

4.   Free

5.   Multi – system

6. Easy to write

About QUnit Tool

 

- QUnit is based on the similar lines as that of the junit which is a unit testing framework. 

- This testing tool works on the JavaScript test suite (that is used by the JQuery project) for testing the code. 

- It comes with various plug – ins which render it the ability to test any generic JavaScript code. 

- Though, QUnit is somewhat similar to Junit, it does uses features of JavaScript for helping with the testing chores in the web browser like starting and stopping the facilities to carry out tests for the asynchronous code. 

- QUnit is quite a powerful unit testing framework used in JQuery mobile projects, JQuery UI and so on.

- You can get QUnit from JQuery CDN and the latest release id version 1.11.0. 

- John Resig is the person behind QUnit.

- Earlier in 2008, QUnit was completely dependent up on JQuery but now it can be used as a standalone application. 

- Common JSunit testing specifications are followed by the assertion methods of QUnit.

- For automated testing writing your own testing framework involves a lot of work since you have to cover all the requirements of JavaScript code. 

- QUnit makes this all easy. 

- You need to include only two QUnit files on the page namely:

QUnit.js: This is the test runner file and

QUnit.css: This styles the test suite so that the results can be displayed.

- Assertions are essential elements of all the unit tests and the QUnit provides 3 namely:

Ok()

Equal()

Deepequal()

What is TOSCA Test suite? Explain the architecture of TOSCA?

TOSCA test suite is another software tool in the line of tools for automated execution of the regression and functional testing. But what makes it different from the other tools in the same category is the TOSCA’s following features:

1. Integrated test management
2. Graphical user interface (GUI)
3. A command line interface (CLI)
4. Application programming interface (API)

History and Evolution of TOSCA

- The developer of TOSCA is TRICENTIS technology and consulting GmbH which is an Austrian company based in Vienna. 

- The year of 2011 saw the inclusion of TOSCA in magic quadrant’s report (developed by Gartner Inc.’s) as a visionary. 

- In year 2011 the TOSCA test suite were recognized as the second most widely used test automation tool by Ross report in New Zealand and Australia. 

- The tool was further recognized by the scientific community when it was presented at two important international conferences namely:

1. Euromicro SEAA and
2. IEEE ICST

- Since then TOSCA has been awarded a number of awards for its web and customer support. 

- TOSCA is software testing tool that serves purposes of numerous other tools such as:

1. Test management tool
2. Test design tool
3. Test execution tool
4. Data generation tool for regression and functional testing

Architecture of TOSCA

The architecture of TOSCA is composed of the following:

1. TOSCA commander: This is the test execution tool of TOSCA which can be used for the creation, administration, execution and analyzation of the test cases.
2. TOSCA wizard: This is the model building tool of TOSCA which can be used for building application model and storing related info in to modules that are essentially XML – GUI maps.
3. TOSCA executor: This TOSCA tool is responsible for the execution of the test cases and displaying the results obtained in the TOSCA commander.
4. TOSCA exchange portal: This TOSCA portal is the place where the exchange and use of the special modules, TOSCA commander components that have already been built and extensions by the customers takes place.
5. TOSCA test repository: This has been made integrated by the TOSCA is responsible for holding the assets. A number of users can access the repository at the same time.

Functionality of TOSCA

Business Dynamic Steering

- The model–driven approach is the concept behind the TOSCA commander.

- This approach focuses in making the whole test dynamic in nature rather than just making the input data dynamic. 

- You can drag and drop the modules and enter the actions and values for validation in order to create the test cases. 

- Making the whole test dynamic is of great advantage for enabling the business – based description of both the automated and manual test cases. 

- This lets the non – technical users (SMEs) to design, automate, maintain and specify the test cases.

- TOSCA supports the following technologies for automation of software tests:

1. Application development environments such as  powerbuilder and gupta.
2. Programming frameworks and languages such as .net, Delphi, WPF, visual basic and java swing/ AWT/ SWT.
3. Host applications (5250, 3270)
4. Web browsers including Mozilla firefox, opera and internet explorer
5. Single – position application programs such as MS excel and outlook
6. Key application programs including Siebel and SAP
7. Protocols and hardwares including Flash, SOAP, USB execution and ODBC

- TOSCA is supported on the following platforms:

Ø  Windows vista Service pack 2

Ø  Windows 7 (both 32 and 64 bit)

Ø  Windows XP service pack 2 and plus.

- The data bases supported are:

Ø  DB v 9.1

Ø  Oracle 10g

Ø  Microsoft SQL server 2005

- TOSCA is being used by 300 customers all over world. 

What are two methods provided by TestPartner for functional test development?

TestPartner is quite a successful GUI software testing tool. Micro focus developed this product with the intention of providing means for functional testing and GUI testing to the software developers and testers who have hard deadlines to work up on. This testing tool helps these software developers and testers to achieve more of testing in less time. 

Two primary methods  are provided by the TestPartner for functional test development:

1. Code oriented development

2. Visual storyboard – based development environment

About Code Oriented Development

- Code oriented development uses the Microsft VBA (visual basic for applications). 

- The major benefit of including this in the development environment is that using it, users can access the rich IDE (integrated development environment). 

- Access to IDE is important since it contains all the core visual basic application libraries plus the capabilities that are inheritable in VBA such as error handling, ability to reference public libraries, debugging and so on.

- A library of VBA – based functionality is provided by the Compuware TestPartner and has been specifically built to be used in the functional test automation.

About Visual Storyboard

- Visual storyboard – based development environment interface is also known as the “visual navigator”.

- It is used extensively for developing the functional test automation. 

- The following things are provided to the user through this capability:

Ø  A screen preview i.e., the screen shot of window of application under test.

Ø A list of test automation steps. These are the steps are the steps that were performed while testing against the screen.

Ø  A story board providing a series of test steps that have been performed against a number of screen previews.

- There is another advantage of this approach which is that the users can access the test automation functionality.

- In addition to this they get the ability to add variabalization, different test logics and so on. 

Advantages and Benefits of TestPartner

- Version 6.3.0 is the latest in the series of Testpartner. 

- Testpartner lets you accelerate the testing process at the same time delivering high quality software products on time. 

- The functional test automation through Testpartner is quite easy and cost effective. 

- Testpartner proves to be a powerful tool for functional test automation. 

- The tool is quite easy to understand and use. 

- Users get intuitive insights through the test analysis and visual test creation. 

- Further, there is no requirement of code which it makes usable even for the non – technical business users. 

- Accelerated testing means that the testers and developers can keep pace with the development and quality is no longer seen as a bottleneck. 

- With the visual and storyboard oriented approach of the Testpartner, such business processes can be captured that can empower the experts for creating the sophisticated test cases without being able to write the script code. 

- The analyzation of the test results is simplified by the Testpartner through its visual storyboard. 

- With this story board, it becomes easy to check where the test actually failed and where the modification is required. 

- Testpartner is well equipped with modular structures and powerful extensions. 

- With these, the technical users can access all the debugging and scripting capabilities of VBA for creating advanced test cases that are repeatable.

- Integration of the test cases that have been written in VBA or visually is possible in Testpartner.

- Tests created by the Testpartner are quick in adapting to the changes made to the application. 

- The test results can be used in incorporating the maintenance changes, thus accelerating the maintenance process. 

- The built – in verification capability of the Testpartner lets you add steps for testing the results.

Explain TestPartner - a GUI Software Testing Tool?

- TestPartner was developed by Micro Focus as a software testing tool especially for testing the graphical user interface (GUI) of the software systems and applications. 

- This testing tool was developed with the intention of empowering the software developers to functionally automate the GUIs of the AUTs. 

- The primary goal was to make the team capable of performing more application testing in a given time period as compared to the manual testing that could be performed in same amount of time. 

- TestPartner offers two basic methods for functional testing:

1. Code oriented development and
2. Visual story board based development

- Recently, the TestPartner version 6.3.0 has been released. 

- It is great product for accelerating the testing process and delivering high quality applications well before the deadline.

- IT managers who have the responsibility of ensuring the quality of the application need to deal with several business challenges that are critical such as:

Ø  Verification of the functionality of the functions i.e., whether or not they are working as expected and meet the business requirements.

Ø  Testing of the multiple heterogeneous technologies simultaneously.

Ø  Keeping up with the fast paced release schedules that are ever changing.

Ø  Striking a balance between the application quality and the associated risks.

- TestPartner provides such functional testing capabilities that very well accelerate the testing process and enables the timely successful delivery of the software.

- This it is known to do at a low cost but with no compromise in the quality. 

- TestPartner achieves this through its unique tiered testing approach. 

- The main feature of this approach is that following it can make it possible for the testers and developers to achieve more in the given time through effective collaboration.

- This software product is even beneficial for the non – technical users. 

- The visual and the contextual approach of the TestPartner lets the non – technical users to be a part of the testing process. 

- For the expert software developers and testers it provides the access to microsoft’s visual basic for the AUTs. 

- This gives them power to cope with the most complex testing problems. 

- TestPartner maintains a special flexibility and focus on the usability of the application allowing the developers to produce more positive results with minimal requirement of training.

- It helps leverage the experienced as well as the non – technical testers to test the applications more efficiently. 

- It encourages the collaboration throughout the development cycle thus achieving greater project effectiveness. 

- Using TestPartner one can even automate the regression testing process, thus quickening the acceptance of the regular updates such as services packs and patches. 

- The documentation produced by the TestPartner is quite clear and free of any ambiguity. - This further accelerates the resolution and identification of various issues related to the application under testing. 

- It makes easy for you to understand the test results so that you feel confident in releasing the software. 

- These test results can be can be used for maintaining the tests, providing better ROI. 

- One can improve the quality of the application leading to lower overall development cost. 

Quality efforts can be accelerated for a number of platforms such as:

1. Web
2. .net
3. Java
4. SAP
5. Oracle
6. Other windows – based distributed applications.

Explain Robot Framework?

The Robot Framework was developed as generic test automation framework for two major tasks namely:

1. Acceptance testing and
2. ATDD or acceptance test driven development

- It makes use of the keyword driven testing approach for achieving the above mentioned two tasks. 

- It has got a very simple and unique tabular test data syntax that is quite easy to follow and this is what that makes robot framework so easy to be used. 

- All this makes the robot framework popular among the testers.

- Test libraries that can be implemented through either java or python can be used for extending the capabilities of the frame work. 

- The users have the choice of creating new keywords from the existing ones. 

- This can be done using the same syntax that is available for the creation of the test cases. 

- Robot framework is actually an open source software. 

- The license it possesses is the Apache license 2.0.

- The Nokia Siemens Networks supports the development of this framework and also owns its copyrights. 

Features of Robot Framework

The robot test automation framework is abundant of features. Its features are:

1. Its tabular syntax is easy to use and can be used for the creation of the test cases in a way that is uniform.
2. Robot framework can work up on three approaches namely:

- Keyword driven testing approach

- Behavior driven development approach or BDD

- Data driven testing approach or DDT.

3. It provides the facility for the creation of higher level keywords that are reusable for the already existing keywords.
4. The reports and logs it generates are quite easy to follow and are based up on HTML.
5. This test automation framework does not depend up on any platform or application.
6. The architecture of the frame work is quite modular in nature that helps in supporting the creation of the tests for even the software systems and applications that possess a number of interfaces all different from one another.
7. It comes with a library API that is quite simple and can be further used for the creation of other test libraries that can be customized.
8. The XML based outputs that the framework provides allow for integrating itself in to the build infrastructure that already exists. These are called continuous integration systems.
9. It also provides a command line interface for the same purpose as that of the XML based outputs.
10. It supports selenium tool for the following things:

Ø  Web testing

Ø  Java GUI testing

Ø  telnet

Ø  running processes

Ø  SSH and so on.

11. The framework comes with a remote library interface, thus enabling the implementation of the test libraries in any desired programming language and distributed testing.
12. The tagging feature provides helps in categorizing the tests and selecting them accordingly for the execution.
13. For variables, it comes with a special built – in support for regulating testing in different environments.

- Test cases can be written either in HTML or in plain text.

- Also, any editor can be used for editing the test cases. 

- The robot test automation framework comes with a graphical development tool called the RIDE or robot IDE. 

- The tool has got a number of features specific to the framework such as syntax highlighting, code completion and so on. 

- Selenium library is an extension to the robot test automation frame work and similarly there are a number of others. 

- However, there are some other languages that can be used for implementing the libraries such as perl, PHP, java script and so on. 

- However, these languages can be used only through a remote library interface.

Explain Oracle Application Testing Suite?

Oracle application testing suite is an effort to provide you with a comprehensive web application testing solution that is quite integrated and has got all the tools that you may require for ensuring the reliability as well as scalability of your applications that are based up on critical business processes. 

Oracle application testing suite has got three main parts namely:

1. Oracle Functional Testing: This is for performing regression testing and functional testing on web applications.
2. Job scheduler: This component of the testing suite is responsible for scheduling the testing of the application.
3. Oracle load testing: This is for carrying out scalability testing, load testing and stress testing on the web applications. This component also consists of some tools that can be very well used for monitoring and reporting on the server side.

- A common set of the visual scripts is what that powers the web applications and therefore they don’t require any programming.

- Also, you don’t need to learn any proprietary language, take training classes or to set up any special proxies. 

- As any changes are made to the application, they are reflected in the visual scripts of the application and the updates are automatically performed. 

- This means that the load tests and the regression tests that you created will be automatically synchronized with the application. 

- This will help you to make the automated regression testing an important part of the development process. 

- The functional testing feature of the oracle application testing suite serves as a tool for functional as well as regression testing and as a script recorder for the whole testing suite. 

- Objects on each and every page are recorded by the functional testing suite and the tests are automatically inserted for the validation of the objects.

- In the visual script you can find the graphical representation of each and every object. 

- The components can be augmented or masked as you require with the help of simple click actions.

- The objects on a page are displayed in the tree hierarchy in the visual script. - Flags are used for indicating the differences between the current version and the baseline.

- With the oracle functional testing the creation, maintenance, and execution of the tests becomes very easy. 

- It comes with the following:

1. An intuitive yet powerful automated test case generator.
2. A special text matching component.
3. Ability of executing the data driven tests via the data bank wizard.

Features of Testing Suite

The features of the testing suite have been highlighted below:

1. Automatic test generation/ visual script technology: This features lets you record and test the whole application with object orient scripts that are reusable. The following are the elements that are automatically captured:

Ø  Elements

Ø  Forms

Ø  Frames

Ø  HTML

Ø  Images

Ø  Image maps

Ø  Links

Ø  Active X controls

Ø  Java applets

Ø  VBscript

Ø  Java script

2. Simple script updating: Scripts are updated as per the changes with a simple click.
3. Graphical test results: Red flags indicate the HTML differences or any failures so that they can be diagnosed.
4. E- spider: Whole of your site is automatically mapped and visual scripts are created for either whole or partial of your application.
5. Data bank wizard: It enables you to create data bank wizards without actual programming. Since the visual scripts reusable they can be used again and again with different inputs every time.
6. Visual test case insertion: This feature lets you add extra test cases to the scripts fore the verification of the server response times, text of the page and form elements and so on.
7. Programming interface

How do you schedule and run tests in Test Director?

In this article we shall see how the tests can be scheduled and run. 

By configuring the conditions the test director can be instructed to postpone the run of the current test till the completion of some other specified tests is over. For example, the test b is scheduled to be run only after the test a finishes with the execution and there is one more test c which is scheduled to run only if the test b passes.

Also, the tests a and b can be scheduled to be executed a day prior to the execution of the test c. the tests and their conditions are displayed by the execution flow in the form of a diagram. 

Steps to schedule tests in test Director

Follow the below mentioned steps to schedule a test run:

1. Firstly, make sure that the test module is in the view mode and if it is  not then first enable it.
2. Second step involves creation of a new test. Click on the execution flow tab in the test lab module. Choose a folder in the test sets tree and click on the ‘new test set’ option. You will get a ‘new test set’ dialog box. Type in the following details:

a)   Test set name

b)   Description

Once you are done click OK and the test set will be added to the test sets tree in the left pane by the test director.

3. Add a test that you want to add to the test set created in the previous step. Using the ‘select tests’ button  to make the test director display the test plan tree in the right pane. Then, type the name of the test to be searched for in the find box in the test plan tree and click find button. Select the searched test and add it to the test set using the ‘add tests to test set’ button.
4. Any number of tests can be added to the test set. To add the tests to the execution flow either simply drag them in to the execution flow area or double click on them.
5. Add conditions using conditions tab. When you will click on the new button a ‘new execution condition’ dialog box will pop up. Select the required test and then passed option. This will instruct the test director to execute the next test only after the successful execution of the previous test. Click OK once done with this and the condition will be added to the run schedule of by the test director in the test dialog box.
6. You can even add a dependency condition to the tests by clicking on the time dependency tab. You will get a field titled ‘run at specified time’, in that specify the date of execution and click OK. Clicking on OK will close the run schedule. The conditions will be displayed by the test director in the execution flow area.
7. Further, if required, some execution condition can also be added to the tests.
8. For rearranging the tests in a hierarchical way, click on the perform layout option. You can then view the dependencies between the tests clearly.  

How the tests are run in Test Director?

We get two options form the test director namely:

a)   Running tests manually and

b)   Automating the tests.

Follow the steps below for the manual execution of a test:

1. Click on the test lab module to display the test lab module.
2. From the test sets select the required test set.
3. From the execution grid select the required test.
4. Clicking on the run will open up a manual runner dialog box.
5. To begin the test run click on the test run. Parameter values dialog box will open up.
6. Assign the parameter values for the test.
7. Click OK and test director will show up the manual runner. The step details dialog box will open up. Perform the execution process step by step.
8. After running all the steps return to the default manual runner display. End the test run by clicking on the end of run button. 

How to run a test automatically in Test Director?

The whole testing process revolves around the execution of the tests. As the changes are introduced in to the software system or application, running tests either manually or automatically becomes mandatory so that the defects can be located and quality can be assessed. 

How are tests run?

- One starts the testing process with the creation of the tests and adding these tests to a test set. 

- Tests are grouped into test sets by the test director so that some specific goals can be achieved. 

- Execution process of the tests can be controlled via the various controls provided by the test director. 

- Along with these controls, there are certain conditions and settings which need to be configured for the execution of the tests as desired by the tester. 

- The date and time can also be scheduled when the tests will be executed. 

- Once the tests have been defined the tester can begin with the execution of the tests. 

- Whenever the tests are executed manually, it is basically the test steps that were defined earlier during the test planning which are executed one by one. 

- The steps are passed or failed by the tester depending up on whether there is a match between the expected results and the actual results. 

- For the automatic run of a test, the selected tool is directly opened by the test director and the test is run. 

- The result hence obtained is exported to the test director. 

- Setting conditions and specifying date and time for the execution of a test both can be done with the help of the execution flow tab.

- In the execution, one thing should be noticed which is that the condition is always dependent on the result of some other specified test in the same flow. 

- Also, the sequence in which the tests are to be executed can be specified. 

In this article we shall see how the test execution can be automated. The tool selected for the execution of the tests is opened directly by the test director and the tests are run on either local or remote machine. It is either choice if you want to run all the tests or some specified ones. 

For running the tests automatically one of the following tools must be installed on the system:

a)   Astra quick test

b)   Quick test professional

c)   Winrunnner

Follow the below mentioned steps:

1. Clicking on the test lab tab will display the test lab module. This is a must for the automation of the tests.
2. The test set you want to execute automatically should be displayed in the execution grid. For doing this click on the execution grid tab and select the required test from the test sets tree.
3. Select a test. For running the winrunner test select the required test or if you want to run an astra quick test or QTP test select the required one. Next clicking on the run button will open up the execution dialog box and the test will be displayed.
4. Configure the test run settings and select the ‘run all tests locally’ option for running the tests on the local machine.
5. For running the tests click on run tests and the tool will be opened automatically by the test director and the tests will be run. The execution progress can be viewed in the status column.
6. Once the execution of the test is complete close the execution dialog box by clicking on the exit option.
7. Also the summary of the test results can be viewed in the execution grid.