Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Davy Boussauw

No description
by

Davy Boussauw

on 16 December 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Davy Boussauw

© 2009 CliniSys Group – Commercial in Confidence

Automatisatie =/ doel op zich

Automatisatie = geautomatiseerde hulp bij het uitvoeren van testen

Doel = uitvoeren van repititieve regressietesten

Doel =/ vinden van meer bugs, maar deze vlugger vinden

Tijd vrijmaken van testers voor het uitvoeren van exploratieve testen

Doel

Davy Boussauw



Tuesday, December 16, 2014

Ranorex - Test automation

CI

Reporting

Test suite:
combined suite of (already existing) TC’s.

Test Case
: set of related recording modules

Recording module / code module:
set of related actions. (small! = reusable)

Test – Actions
: Test step (e.g. click, key sequence, validate,...)








Ranorex terminology

I : Test Specification (SpiraTest)
II : Scripting Test Specification
III : Run Scripts
IV : Analyze Test Run results

Workflow

Repository: Logical name

Repository

Test Actions

Module view

Ranorex UI

Recording module

Test case

1. Project view
2. Module browser
3. Project / file view

Ranorex UI

© 2009 CliniSys Group – Commercial in Confidence

© 2009 CliniSys Group – Commercial in Confidence

© 2009 CliniSys Group – Commercial in Confidence

© 2009 CliniSys Group – Commercial in Confidence

© 2009 CliniSys Group – Commercial in Confidence

© 2009 CliniSys Group – Commercial in Confidence

General overview (successfully, failed or blocked) + global parameters
Each executed test case and all its child modules can be analyzed in depth (+current parameters) by expanding a particular test case.


Vragen?
Test Suite

CyberTrack
CyberLab
Glims
Known limitations
Ranorex
Rx UI
(Automated) Testing
Reporting & integration
@ Mips
Ranorex can be used for
Desktop
,
web
&
Mobile
software.
Ranorex technology

© 2009 CliniSys Group – Commercial in Confidence

Desktop:
.NET
, WinForms, WPF, Win32, VB6, Java, Qt, Delphi, PowerBuilder, SAPgui, MFC, ActiveX, Microsoft Visual FoxPro, Microsoft Office GUI, Microsoft Access, Microsoft Dynamics AX, Microsoft Dynamics CRM, Microsoft Dynamics NAV, Air,
Infragistics
, DevExpress, ComponentOne, Janus, Syncfusion, Telerik, SkinSoft and many more..
Web:
HTML, HTML5, JavaScript, Ajax, Silverlight, Flash, Flex, Air, ASP.NET, Google Web Toolkit, YUI library, Ext JS, Ext.Net, Java applet, jQuery, Sencha GXT, Dhtmlx, Sweetdev Ria, MochiKit, MooTools, Pyjs, Rico (Ajax), SmartClient, midori JavaScript Framework, Echo (framework), script.aculo.us, Enyo, ZK (framework) and many more, along with
cross-browser testing
for Internet Explorer, Firefox, Chrome and Safari
Mobile:
Native iOS apps, native Android apps, Xamarin.iOS, Xamarin.Android, PhoneGap, mobile web testing for iOS, Windows Mobile app
Ranorex

© 2009 CliniSys Group – Commercial in Confidence

Ranorex is used to perform GUI Testing.
So we test all possible user interactions like keyboard and mouse events (exactly as a user would do it ).

We can also verify graphical control elements of the UI (are all buttons, icons, images,... displayed).
@ Mips
Currently:
Future:
CBT
: main features automated
CBL
: 'stopped' automation
Glims
: started since 2/3 weeks
Manual builds: run when needed (release Glims / CBT)
Automated build together with product builds
Running after every build (@night)
All products (CBT, CBL, Glims, CL?)

Wat is er geautomatiseerd?
Om bij het analyseren van de testlogging het doel van de test te kunnen achterhalen
Om bij eventuele fouten te kunnen achterhalen wat de bedoeling van de test is/was.
Link SpiraTest - Ranorex

© 2009 CliniSys Group – Commercial in Confidence

Modifications testen






Regressie testen

Testing

Wat automatiseren?

© 2009 CliniSys Group – Commercial in Confidence

© 2009 CliniSys Group – Commercial in Confidence

Controleren wat de ontwikkelaar heeft aangepast
Relatief beperkt (afhankelijk van tijdsdruk)
Onmogelijk elke impact te voorspellen
Werkt het geheel nog steeds?
Set van testen die we iedere release opnieuw uitvoeren
Beperkte regressietestset vs 'complete' testset
Automatiseren we NIET direct -> enkel als het belangrijk genoeg is om in de regressietesten op te nemen.
Modifications testen






Regressie testen

SpiraTest
Analyse - beperkingen (zie later)
Jenkins
Glims
No 'old' progress browsers
No manual user input possible (e.g scan)
56 TC
16TC
Stand van zaken:
Zie SpiraTest
63 TC's automated / 338 Regression TC
+- 18%
Voornamelijk Routine & UI
DEMO
Glims
'Problemen':
Mengeling van oude progress editors en nieuwe '.Net' elementen
.Net elementen: unieke naam
Progress elementen: GEEN unieke naam, maar een controlID dat telkens een ander nummer heeft...
Glims
Maar ook:
Wat als een TC faalt?
-> teardown & setup
Full transcript