Ranorex Forum

Imports System.IO
Imports System

Public Class KeywordDriver
	
	Dim keywords as String()
	
	Public Sub New(keywordFile As String)
		If file.Exists(keywordFile) Then
			parseKeywords(keywordFile)
		Else
			Exit Sub
		End If
	End Sub
	
	Public Sub start
		executeKeywords
	End Sub
	
	Private Sub parseKeywords(fileName As String)
		keywords = file.ReadAllLines(fileName)
	End Sub
	
	Private Sub executeKeywords
			For Each keyword As String In keywords
				If trim(mid(keyword,1,2)) <> "//" And trim(keyword) <> "" Then
					Dim strParams As String() = split(keyword,",")
					Dim parameters (strParams.Length-2) As  Object
					For x As Integer = 0 To strParams.Length - 2
						parameters(x) = trim(strParams(x + 1))
					Next
					startMethod(strParams(0),parameters)
				End If
			Next
	End Sub
	
	Public Sub startMethod(methodName As String,  parameters() as object)
			Dim names as String() = split(methodName,".")
			Dim a As system.Reflection.Assembly = system.reflection.Assembly.GetExecutingAssembly
			For Each t as system.Type In a.GetTypes
				If t.Name = names(0) Then
					For Each m As system.Reflection.MethodInfo In t.GetMethods
						If m.Name = names(1) Then
							Dim x As Integer = 0
							For Each paramInfo As System.Reflection.ParameterInfo In m.GetParameters()
								parameters(x) = convert.ChangeType(parameters(x),paramInfo.ParameterType)
								x = x + 1
							Next
							Dim o As New Object
							m.Invoke(o,parameters)
						End if
					Next
				End if
			Next
	End Sub
	
End Class

artur_gadomski wrote:I have made a small proof of concept project that uses RobotFramework and Iron Python to execute Ranorex code. Reporting needs a bit of ironing out but other than that everything seems to look fine.

import os
import sys
import clr
clr.AddReference("KeywordTest.dll")
import KeywordTest
from elementtree import ElementTree

class LoginLibrary:

    def __init__(self):
        self._prog = KeywordTest.Program()

    def connect(self):
        self._prog.Connect()

    def close(self):
        self._prog.Close()

    def capture_screenshot(self):
        self._prog.CaptureScreenshot()

    def start_log(self, suite):
        self._prog.SetupReport(suite)
        
    def should_login(self):
        self._prog.ShouldLogin()

using System;
using System.Collections.Generic;
using System.Diagnostics;
using System.Linq;
using System.Reflection;
using System.Text;
using Ranorex;
using Ranorex.Core.Reporting;

namespace KeywordTest
{
    public class Program
    {
        public void Connect()
        {
            string path = "/form[@controlname='DialogLoginForm']/container[@controlname='_buttonsPanel']/button[@controlname='btnConnect']";
            Report.Info("Clicking connect button");
            Button b =
                "/form[@controlname='DialogLoginForm']/container[@controlname='_buttonsPanel']/button[@controlname='btnConnect']";
            b.Click();
            Delay.Seconds(11); // TODO: static delay can not be changed bacause connecting might fail.
        }

        public void CaptureScreenshot()
        {
            Report.Screenshot();
        }

        public void SetupReport(string suite)
        {
            TestReport.Setup(ReportLevel.Debug, "Log.rxlog", false);
            TestReport.BeginTestSuite(suite);
            TestReport.BeginTestCase("Case");
            TestReport.BeginTestModule("Module");
        }

        public void StopReport()
        {
            TestReport.EndTestModule();
            TestReport.EndTestCase();
            TestReport.SaveReport();
            
        }

        public void ShouldLogin()
        {
            string path = "/form[@controlname='DialogLoginForm']/container[@controlname='_buttonsPanel']/button[@controlname='btnConnect']";
            Report.Debug("Looking for connect button.");
            Button b;
            bool buttonExists = Host.Local.TryFindSingle(path, new Duration(1000 * 20), out b);
            if (buttonExists)
            {
                throw new Exception("Could not login.");
            }
            Report.Info("Logged in.");  
        }
    }
}

omayer wrote:It will be very helpful if somebody explain what are these code doing.
Thanks Beginner

atom wrote:To me keyword frameworks are a thing of the past... (when automation had to be "dumbed down" to non programmers)

• A keyword framework also allows you to include non-programmers into the testing and development process, such as business users, managers, customers. They can help specify/define the tests via the keywords and their arguments. It's like writing a test in English vs .NET/C# class method calls. It can help in the ideal situation, as even QA/testers with programming backgrounds and programmers are not fully aware of all the cases that need to be tested. Customers and business stakeholders know more of the expected functionality than we who develop/test it, because they defined it in the first place.

• Not all QA and testers, even with "Engineer" in their title (not sure about "software (development) engineer in test" / SDET though), are fully qualified with programming backgrounds as far as I've observed. It is great that we're moving towards SDET, programming minded for test automation, but we're not fully there yet either. Vendors still tout record/playback features for their test tools.

atom wrote:My advice if your going to do this is write you action classes implementing a common interface. You can then develop a small GUI to load all your actions from a DLL, and you can place your action sequence into a DataGrid, and use a PropertyGrid to set the action parameters. Make it all serialisable, and you can save/reload the scenario to xml. Develop a "runner" that you do execute your saved scenarion from the xml file also. This design will mean you can then ask developers to add to your action library by just writing a class implementing your interface!

atom wrote:You should take a look to the new "Behaviour Driven Testing" tools around... this allows non technical people to write their tests in a very simple language, that an automation engineer can then implement. Take a look at Cucumber for example (http://cukes.info/). Also Fitness allows this also to some extent allowing non technical people to write tests as wiki pages, which can then implemented.