Skip to main content

Change TestPartner script automatically

This is an ugly hack. Please be careful with this code as it is using an undocumented feature. Code below will allow you to modify a test script using VBA. Test script is an asset within TestPartner application, so if you are not using TP this may not apply to you.

'------------------------------------------------------------------------------
' Develop by    : Techno.Scavenger
' Licensed to   : Mankind
' Date          : 11Oct2008 @ 6:55 PM + 8 GMT (Saturday @home)
' Warranty
' THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
' IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
' FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
' “Techno.Scavenger” OR ANY OTHER CONTRIBUTOR BE LIABLE FOR ANY CLAIM,
' DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
' OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
' USE OR OTHER DEALINGS IN THE SOFTWARE.
' Note:
' You can do whatever with this code
'------------------------------------------------------------------------------
Option Explicit
Sub Main()
TestAdd
End Sub
Sub TestAdd()
Dim t As New TPApp
Dim pCount As Integer
Dim p As Integer
Dim sCount As Integer
Dim sName As String
Dim tp As TestPartner.TPProject
Dim ts As TestPartner.TPScript
Dim tsx As TestPartner.TPScriptEx

t.Login "admin", "admin", "TestPartner_SQL", 1
t.Show
pCount = t.Projects.Count
For p = 1 To pCount
If t.Projects.Item(p).Name = "Common" Then
Debug.Print t.Projects.Item(p).Name
Set tp = t.Projects.Item(p)
Dim iSCount As Integer
iSCount = tp.Scripts.Count
Dim iSIdx As Integer
For iSIdx = 1 To iSCount
Set tsx = tp.Scripts.Item(iSIdx)

Set ts = tp.Scripts.Item(iSIdx)
If ts.Name = "TestExecOther" Then

tsx.OpenToLine 2
Sleep 1, tpPauseSeconds
SendKeys "^a", True
Sleep 1, tpPauseSeconds
SendKeys "{BACKSPACE}", True
Sleep 1, tpPauseSeconds
SendKeys "~", True
SendKeys "Sub Main", True
SendKeys "~", True
SendKeys "Msgbox ""Hello 6""", True
SendKeys "~", True
SendKeys "^S", True
Set tsx = Nothing
SendKeys "%FC", True
SendKeys "~", True
End If
Next
End If
Next
t.Logout
Sleep 5, tpPauseSeconds
Set t = New TestPartner.TPApp
t.Login "admin", "admin", "TestPartner_SQL", 1
t.Show
pCount = t.Projects.Count
For p = 1 To pCount
If t.Projects.Item(p).Name = "Common" Then
Set tp = t.Projects.Item(p)
iSCount = tp.Scripts.Count

For iSIdx = 1 To iSCount
Set ts = tp.Scripts.Item(iSIdx)
Debug.Print ts.Name
If ts.Name = "TestExecOther" Then
ts.Execute -1, -1
Do While t.PlaybackInProgress
Sleep 1
Loop
t.Logout
End If
Next

End If
Next
End Sub


~ts

Comments

Anonymous said…
Ahh nice! I was just wondering if this type of stuff was possible. Well done!

Popular posts from this blog

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re