Even though automation scripts are intended to drive the application under test there are cases when communication with tester is required. With TestComplete, we have a vast arsenal of predefined GUI controls for that (and those, acquainted with Delphi, will be pleasantly surprised by the way it’s organized).

Today’s post provides an example of creating and using dialog with custom event handlers – whenever script user provides input, event handler may be used to provide a customized response.
In the scope of the exercise let’s use the following task.

• Setup form prompts to choose an environment where test plan is to be run
• User can choose one of predefined environments: DEV, SIT, UAT
• Receives a response as a url of the environment
• User can leave suggested by default test data file or can type filepath directly

Preparing Modal Form

We begin with a sample form.

Add Edit Controls, Buttons, and Labels

Set Object Properties

Form

• Name – object name to use in the code; ‘Security’ in my example
• Caption – title of the window when the form is displayed

Label controls

• Caption – displayed text

Edit Box Control

• Name – object name to use in the code; ‘ShowUrl’ in my example
• Text - initial value
• ReadOnly = True – because user can’t input Url directly

Combo Box Control

• Name – object name to use in the code; ‘Environment’/’TestData’ in my example
• Properties.Items – items to select; ‘DEV’, ‘SIT’, ‘UAT’ in my example
• ItemIndex = 0 – initial selection
• Properties.DropDownListStyle = lsFixedList – for Environment combobox
• Properties.DropDownListStyle = lsEditList – for TestData combobox

Buttons

• Caption – displayed text; ‘OK’/’Cancel’ in my example
• Cancel = True – for ‘Cancel’ button
• ModalResult = mrCancel – for ‘Cancel’ button
• Default = True – for ‘OK’ button
• ModalResult = mrOK – for ‘OK’ button

Set Event Handler

Properties

Path

Code

Public Sub Setup_Environment_OnChange(Sender)
  Dim sEnvironment

  sEnvironment = UserForms.Setup.Environment.Text

  Select Case sEnvironment
    Case "DEV"
      UserForms.Setup.ShowUrl.Text = "http://dev/"
      UserForms.Setup.TestData.Text = "W:\Test Suite\Data\DEV.xlsx"
    Case "SIT"
      UserForms.Setup.ShowUrl.Text = "http://sit/"
      UserForms.Setup.TestData.Text = "W:\Test Suite\Data\SIT.xlsx"
    Case "UAT"
      UserForms.Setup.ShowUrl.Text = "http://uat/"
      UserForms.Setup.TestData.Text = "W:\Test Suite\Data\UAT.xlsx"
  End Select

End Sub

Example

Public Function Form1()
  Dim objDlg
  Dim sEnvironment, sTestData
  Dim Result

  'Get object's instance
  Set objDlg = UserForms.Setup

  'Execute
  Result = objDlg.ShowModal

  If Result = mrOK Then
    'retrieve the selected input
    sEnvironment = objDlg.Environment.Text
    sTestData = objDlg.TestData.Text
  Else
    'Respond
    MsgBox "Execution cancelled", vbOKOnly
    'exit function or finalize execution
  End If

End Function

Even though automation scripts are intended to drive the application under test there are cases when communication with tester is required. With TestComplete, we have a vast arsenal of predefined GUI controls for that (and those, acquainted with Delphi, will be pleasantly surprised by the way it’s organized).

Today’s post provides an example of creating and using ‘Username/Password’ dialog.
But, first, a couple of words why automation scripts would need one.

No, this is not an authorization to run the scripts. This is for the scripts.
Maybe you need to connect to the database. Or run the scripts with administrator’s permission. Or it’s just a security requirement from your stakeholders.

Whatever it is, you better not store such sensitive data in a file or the source code. Make them exist only during run-time.

Preparing Modal Form

We begin with a sample form.

Add Edit Controls, Buttons, and Labels

Set Object Properties

Form

• Name – object name to use in the code; ‘Security’ in my example
• Caption – title of the window when the form is displayed

Label controls

• Caption – displayed text

Edit Box Controls

• Name – object name to use in the code; ‘EditUsername’/'EditPassword’ in my example
• EditPassword.Properties.EchoMode = eemPassword – to mask password characters

Buttons

• Caption – displayed text; ‘OK’/'Cancel’ in my example
• Cancel = True – for ‘Cancel’ button
• ModalResult = mrCancel - for ‘Cancel’ button
• Default = True – for ‘OK’ button
• ModalResult = mrOK - for ‘OK’ button

Example

  Dim objDlg
  Dim sUsername, sPassword
  Dim Result

  'Get object's instance
  Set objDlg = UserForms.Security

  'Execute
  Result = objDlg.ShowModal

  If Result = mrOK Then
    'retrieve the input
    sUsername = objDlg.EditUsername.Text
    sPassword = objDlg.EditPassword.Text
  Else
    'Respond
    MsgBox "Execution cancelled", vbOKOnly
    'exit function or finalize execution
  End If

Even though automation scripts are intended to drive the application under test there are cases when communication with tester is required. With TestComplete, we have a vast arsenal of predefined GUI controls for that (and those, acquainted with Delphi, will be pleasantly surprised by the way it’s organized).

The second post in the series provides an example of using ‘File Open’ dialog.

We begin with a sample form.

Add ‘TOpenDialog’ Icon

Set Dialog Properties

The property names are straight-forward, so I cover only main ones.

• Name – object name to use in the code;
• InitialDir – folder to begin browsing from;
• Filter – to specify what filetypes to display;
• FileName – will contain the full pathname of the file upon successful selection;
• Options\ofPathMustExist – set True if selection accepts only existing files;
• Options\ofFileMustExist - set True if selection accepts only existing files;

These properties can be set in the Property Editor or directly in the code at run-time as in the example below.

Example

'Get object's instance
Set objDlg = UserForms.PlanOpenDlg
'Assign path
objDlg.OpenDialog.InitialDir = "C:\FakePath\Test Plans"
'Set filter
objDlg.OpenDialog.Filter = "XML Test Plans (*.xml)|*.XML"
'Execute as modal and get the status
If objDlg.OpenDialog.Execute Then
  'retrieve the selected file
  sTestPlan = objDlg.OpenDialog.FileName
Else
  'Respond
  MsgBox "Execution cancelled", vbOKOnly
  'exit function or finalize execution
End If

Even though automation scripts are intended to drive the application under test there are cases when communication with tester is required. With TestComplete, we have a vast arsenal of predefined GUI controls for that (and those, acquainted with Delphi, will be pleasantly surprised by the way it’s organized).

Today’s post walks through the main preparation steps.

Add New Project Item

Select Project Item Type – ‘User Forms’

Add New Item into ‘User Forms’

Add New Item into ‘User Forms’ – Create a New Form

You end up in the Form Editor

Note that you can add GUI controls from 4 main categories:

• ‘Editors’
• ‘Helpers’
• ‘Extra’
• ‘Dialogs’
• ‘Buttons’

Description

Get token string from the source string. Position is relative, defined by another token-keyword and a number.

Implementation

Public Function GetTokenByKeyword(ByVal strSource, ByVal chrDelimiter, ByVal strKeyword, ByVal intNumber, ByRef strToken)
	Dim Tokens, intCount, intIndex
	Dim i, boolRC

	Tokens = Split(strSource, chrDelimiter)
	intCount = UBound(Tokens)+1
	intIndex = -1

	For i=0 To intCount-1
		If Regex_Test(Tokens(i),strKeyword) Then
			intIndex = i
			Exit For
		End If
	Next

	If intIndex = -1 Then
    strToken = ""
		GetTokenByKeyword = False
		Exit Function
	End If

	If (intIndex+1+intNumber) > intCount Then
    strToken = ""
		GetTokenByKeyword = False
		Exit Function
	End If

	If (intIndex+1+intNumber) < 0 Then
    strToken = ""
		GetTokenByKeyword = True
		Exit Function
	End If

	strToken = Tokens(intIndex+intNumber)
	GetTokenByKeyword = True
End Function

Description

Get token string from the source string. Position is absolute, defined by number.

Implementation

Public Function GetTokenByNumber(ByVal strSource, ByVal chrDelimiter, ByVal intNumber, ByRef strToken)
	Dim Tokens, intCount

	strSource = ReplaceEx(strSource, "  *", " ", False)
	Tokens = Split(strSource, chrDelimiter)
	intCount = UBound(Tokens)

	If  intNumber > intCount Then
		GetTokenByNumber = FALSE
		Exit Function
	End If

	strToken = Tokens(intNumber-1)
	GetTokenByNumber = TRUE
End Function

(Click on the picture to view it full-size in a separate browser window)

Now, I won’t be putting much of details here. I think, the best would be to come and engage in person. But for those who don’t live in Greater Toronto Area, here’s someting…

I really enjoyed conversation with Fiona Charles about the subject:

I had even longer discussion with Adam White, the organizer of the event,  and Michael Bolton, about the following proposition -

- but we still left it only partially covered.

Date Macro

Date Calculations

One of them, taken in April, is the course of Rapid Software Testing. I wrote about my experience and takeaways, as well as proudly gave a personal endorsement.

Another course, similar and different at the same time, is Black Box Software Testing (Foundations level), which was taken in Autumn. Same as with the RST course, I’ve got a unique blend of experiences.  And I want to say more about it.

The course itself is organized in a “research lab” style. It actually reminded me of my happy student years. Theory and practice are given in an excellent mixture, and the course has a potential of keeping knowledge-thirsty students busy for 40 hours a week. (Although you don’t have to spend that much time to pass the exam. But I found the assignments so addictive that I worked even on those not given to me.)

In this sense, the Foundations level course will be a true testament of skills even for someone considering himself (or herself) a senior tester.

The course aims for the following learning objectives:

• Understanding key testing challenges; choosing the strategy to meet your actual needs under present constraints.
• Rapid learning, as well as learning through collaboration and reflection.
• Critical thinking and precision in reading.
• Efficient and effective communication, and well-structured feedback.
• Understanding diversity of definitions in software testing terminology.
• “Complete” vs. “Good Enough” testing.
• Heuristic approach.
• Programming fundamentals.
• What is coverage?
• Measurement and metrics. 

That’s a lot for just 3 weeks! But what makes the course really special is the tight collaboration it requires and encourages. I felt pretty strong on many topics yet I was deeply engaged in the assignments either finding new aspects for myself or supporting fellow students. We had quite a group! I wish at my day jobs I’d always meet such a strong passion for testing and learning.

If, at this point, you haven’t signed up for the course yet, here’s another argument to consider: you will get to work with a star team of instructors. For the particular course I was taking, our instructors and facilitators were Cem Kaner, Rebecca Fiedler, Michael Larsen, Selena Delesie, and Brian Osman. – And I’m very thankful to them for all the feedback and coaching given.

On a final note, I want to say: if the RST course with Michael Bolton was the most insightful and inspiring experience of this year, the BBST course was the most challenging and motivating experience, and I look forward to taking Advanced classes.