What are main features of TestComplete?

Many of the software applications are being written as web–based applications that can be run in a browser. The measure of effectiveness with which these applications are tested varies from organization to organization. 

- Test complete automated testing tool offers the answer to this demand. 

- For tests such as regression tests, responsiveness can be generated only through automated testing tools as such. 

- Automated testing is the way to provide many benefits including repeat-ability and speed of the test execution. 

- Test automation is known to induce long term efficiency in a software system or application.

- Developers also get a rapid feedback and can carry out unlimited iterations of the tests.

- Reporting gets customized and finding defects that were missed during the manual testing becomes easy.

-  However, automation always does not prove to be advantageous.

Features of TestComplete

Test complete  testing tool comes with certain features which we shall state now:

1. Keyword testing: This tool comes with a keyword–driven test editor that is built– in and consists of many keyword operations corresponding to the appropriate automated testing actions.
2. Test record and play back: This tool records the key actions which are required to play back the test. All the actions other than the required ones are then discarded.
3. Full featured script editor: This is another built – in editor using which the test scripts can be written manually. This editor comes with some special plug – ins that provide further assistance.
4. Script debugging features: This feature lets you stop before every statement that can be executed so that you can keep a track of what is going on and make changes accordingly.
5. Access to properties and methods of the objects: The names of all the visible elements can be read by this tool including internal elements of the following applications:

a)   Delphi

b)   C++builder

c)   .net

d)   WPF

e)   Java

f)    Visual basic etc.

Also this tool enables the access to values through test scripts so that they can be verified and used in the tests.

6. Unicode support: Tool has a Unicode character set support which enables the user to test the applications that are non – ASCII and use characters such as Hebrew, greek, Arabic, katakana and so on.
7. Issue–tracking support: This tool comes with issue tracking templates which can be deployed for the creation as well as modification of the items that reside in issue – tracking systems. The tool currently provides support for the following:

a)   Microsoft visual studio 2010,2008 and 2005 team system

b)   Bugzilla

c)   Automated QA AQdev team

8. Open architecture (COM based): An open API, COM interface forms the basis for the test complete’s engine. This makes this tool independent of the source – language and enables it to read the debugger info. It can use this info during run time via debug info agent of test complete.
9. Test visualizer: This feature of test complete lets you take screen shots of the test recording as well as play back thus allowing you to make comparisons among the actual as well as the expected screens during the run time.
10. Support for plug–ins: This feature allows the third party vendors to connect with test complete via their software systems and applications. 

What is the built-in recovery system in Silk Test?

With the in – built recovery system of the silk test automation tool it has been made possible to restore the application under test to its stable state which it was in before it crashed, failed or hanged. The stable state to which the recovery system of the silk test restores the application under test or AUT is called the base state of the application software. 

The test automation counterpart of the silk test i.e., the winrunner does not support this feature. The recovery system comes in to action whenever the application under test fails ungracefully. 

For client server based applications there are 4 major tasks that are carried out by the built – in recovery system of the silk test. Those 4 major tasks have been listed below:

1. Ensuring the continuous running of the web browser.
2. Restoring the application back to its default size if it has been minimized by the user.
3. Setting the working status of the application as active.
4. Closing the other dialog boxes or child windows that have popped up.

On the other hand the below mentioned are the tasks that are carried out by the built – in recovery system of the silk test for the application software that are browser based:

1. Waiting for the browser to restore itself to the active mode if it has been inactive for a long time.
2. Ensuring that the various below mentioned elements are displayed:

a)   Status bar

b)   Text field

c)   Location

d)   Browser tool bars and so on.

- The data regarding this built – in recovery system is stored in a file by the name of defaults.inc which can be found in the same directory where the silk test has been installed. 

- Most of the actions that are carried out on the application under test are when the application is in the default base state. 

- In this state, all the actions are based up on the default properties.

- So, whenever a test case or script is executed the recovery system gets invoked automatically.

- However, the flow of control is different when the tests are run based up on some main function or a test plan. 

- Here, when a test case starts executing via the silk organizer the same test case gets the control first. 

- But before the execution of any test case, a function is called namely “default test case enter”. 

- This function is called with the purpose of calling the set app state function which in turn will invoke the default function “default base state”. 

- Following this the execution of the test case begins. 

- In any of the either cases the control is passed to the default test case exit function:

1. If the test case finishes with its execution or
2. If the test case encounters an error while execution

- The default test case exit function keeps the record of the logs for the exceptions in the test case execution and later calls the set base state function which in turn calls the default base state function. 

- Whenever the tests are run via a main function instead of one two recovery functions are invoked in the same way. 

- But here the difference is that instead of calling default test case center the function called is “default script enter” before the scripts start running. 

- The value of this function is NULL by default. 

- When the last test case has finished executing the “default script exit” function is called. 

- The purpose of this function is to log the errors or faults that occurred outside the test case.