Is there any problem in using scripts created on v6.0 to 6.5 or higher versions?

In some cases, it may happen that while trying to automate a java swing application using an early version of silk test such as the silk test 5.0.3. You found that the objects and controls in the application window of the application under test or AUT might not be recognizable by the silk test. 

This is just an example of problems of such category and at times you may wonder if the higher versions such as the silk test v 6.0 or silk test v 6.5 are suitable for automating your application or not? Or does the silk test comes with some extensions or add – ons as an alternate for overcoming such situations. 

The version 6.0 of the silk test is known to have some bugs in it, however, the Segue software has known to resolve these known issues. Actually, advancing form a lower version to a higher version of the silk test must not pose a problem. 

Though this is a general statement that we made on the basis of observation of several instances, it is not necessary that it should turn out to be true in all the cases. You may face some problems with the scripts that will work on an earlier but not on higher versions such as 6.0 and above because the object recognition patterns in both of them are not the same and vary from version to version. 

There are certain situations where the two paths of the script might be used for performing the same action but based up on the version. 

The silk test version 6.0 and silk test version 6.5 are somewhat similar and though no problems are experienced in advancing from version 6.0 to version 6.5 of the silk test. 

The various client forms of silk test are available such as those stated below:

1. Silk test classic: This client of the silk test makes use of the domain specific language called “4test” for scripting of the test automation scripts. This language just like the C++ language is an object oriented language. Just like C++ it also makes use of the Object Oriented concepts such as following:

a)   Inheritance

b)   Classes and

c)   objects

2. Silk 4J: This client of the silk test enables one to follow test automation by using java as the scripting language in eclipse.
3. Silk 4 net: This client of the silk test also enables one to follow test automation by using VBScript or sometimes using C# as the scripting language in the visual studio.
4. Silk test work bench: This client of the silk test enables the testers to carry out the automation testing using VB.net as the scripting language as well as on a visual level.

Below stated is the list of the silk test versions that have been released till now:

1. Borland silk test 13- june 2012
2. Micro focus silk test 2011 – November 2011
3. Micro focus silk test 2010 R2 WS 2 – may 2011
4. Micro focus silk test 2010 R2 – December 2010
5. Micro focus silk test 2010 – july 2010
6. Silk test 2009 – august 12, 2009
7. Silk test 2008 SP1 – jusly 2008
8. Silk test 2008 – april 2008
9. Silk test 2006 R2 service pack 2 – September 2007
10. Silk test 2006 R 2 service pack 1 – june 2007
11. Silk test 2006 R2 – January 2007
12. Silk test 2006 – September 2006
13. Silk test 8.0 – may 2006
14. Silk test 7.6 – September 2005
15. Silk test 7.5 – june 2005
16. Silk test 7.1 – October 2004
17. Silk test 6.5 – November 2003
18. Silk test 6.0 – November 2002
19. Silk test 5.0.1 – September 1999
20. QA partner 4.0 – November 1996