Microsoft Test Manager – FUEL for test automation

(this is a follow-up post to this one: http://sudiptopaul.blogspot.com/2011/12/using-aspnet-page-state-and-theme-to.html)

Traditionally Test Management and Test Automation tools have been remotely related to each other.

Microsoft’s Test Manager changes this -

Manual Testers contribute effectively by creating action recordings for each test
Common portions of test steps can now be grouped into what is called as Shared Steps – again manual tester can create independent action recordings for these
Test Manager enables these action recordings to serve as active inputs to test automation – separate class is created for each test case, and a reusable function for each shared step
- This is very elegant as it saves the test automation engineer an amount of time required to refactor common portions of longish test path recordings
- The Manual Tester gets to contribute in the Keyword definition phase – an important thing to do, because they are the subject matter experts!

Here’s a video that demonstrates this:

Microsoft Test Manager – FUEL for test automation

Comments

Experimenting with Visio and VBScript

This diagram is created: using this code: Copy the code: Option Explicit Dim strVSDPath, filesys Dim vsoApplication, vsoDocument, vsoPages, vsoPage Dim vsoMaster1, vsoMaster2, vsoStencil Dim vsoShape1, vsoShape2, vsoConnector1 Dim itr Const visAutoConnectDirDown = 2 'Connect down. Const visAutoConnectDirLeft = 3 'Connect to the left. Const visAutoConnectDirNone = 0 'Connect without relocating the shapes. Const visAutoConnectDirRight = 4 'Connect to the right. Const visAutoConnectDirUp = 1 'Connect up. ' Visio file to be created. strVSDPath = "D:\Workspace_Visio\TestRunFlow.vsd" 'delete any previously existing Suite file Set filesys = CreateObject("Scripting.FileSystemObject") If filesys.FileExists(strVSDPath) Then filesys.DeleteFile strVSDPath End If Set filesys = Nothing &#

Excel Automation and a palatable QTP Suite

Excel automation and VBScript can be used to create a test suite that can control the run sequence of QTP scripts and present a Summary report of the automation run cycle. Its simple enough to double-click an icon and the VBScript program will create an excel sheet, populated with all the scripts from a Test folder. Here’s the folder structure: Click here to get the files. The CreateSuite.vbs program creates an excel sheet .. .. and populates it with all the QTP scripts from the Tests folder (folder hierarchy within the Tests folder does not matter, a valid script folder will be fetched). Here’s how the excel sheet looks after running the CreateSuite program: This Test Suite has been created in the TestSuite folder, as the Suite.xls file: Once the list of tests is available, one can choose to configure a subset of the listed tests to be run, like in the case below, we turn off the fourth test: Now that the list of tests to be run is ready, we

QTP – search sub-folders for existence of QTP scripts

Suppose we want to report on all subfolders in a specific root folder that contain script files. Consider the example folder structure here – ODBC_MYSQL, ODBC_SQLEXPRESS and Test1 are the folders that have QTP scripts: Here’s a VBScript program that takes the root (start) folder as input, and iterates all subfolders recursively to report on the ones that are actual QTP script folders: Note: This program can be run directly as a VBScript program, or from within a QTP script by toggling the comment between lines 17 and 18. (p.s.: if Print statement does not work on specific version of QTP, use the Msgbox statement. For real world test automation projects, do not use either – to avoid human intervention!) On running the program, Folders across various levels (Level 2, 3) get reported!

Nuts, bolts and bytes

Search This Blog