• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Alexandre Iline Rit 2010 Java Fxui
 

Alexandre Iline Rit 2010 Java Fxui

on

  • 406 views

 

Statistics

Views

Total Views
406
Views on SlideShare
406
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Note that in reality all the verifications should be done throwg waiting
  • Effectiveness is estimated under assumtion that the testing is thoruogh and there are many tests
  • This is a well accepeted practice nowadays. However it is not really possible without testing. And it is not really possible with manual testing as the turnaround is too long to rely on.
  • This is a well accepeted practice nowadays. However it is not really possible without testing. And it is not really possible with manual testing as the turnaround is too long to rely on.
  • If we get to it, I will be howing figures which explain why do we think so
  • It is not a toy
  • ditto
  • The values of course depend on how the fast product is changing The estimations are for NetBeans – we went throughthis stage Now would happen if the combobox is replaced by color chooser page up test would fail, 'cause it's looking for combobox page down Most importantly ... all tests would fail!
  • Obvious solution

Alexandre Iline Rit 2010 Java Fxui Alexandre Iline Rit 2010 Java Fxui Presentation Transcript

  • Testing JavaFX UI Tips from JavaFX quality team Alexandre (Shura) Iline Java and JavaFX quality architect Oracle
  • Agenda
    • UI testing overview
    • Test automation approaches
    • Jemmy library
    • Test automation effectiveness
    • Test library design approaches
  • UI testing … by Wikipedia «GUI software testing is the process of testing a product that uses a graphical user interface, to ensure it meets its written specifications.»
  • UI testing … most often ... «Checking whether usage of a product UI leads to results expected by the the person who performs testing »
    • Start text editor
    • Push «File/Open»
    • Verify file chooser directory
    • Select some file
    • Verify editor area content
    • Verify application title
    • Verify buttons availabilities
    • ....
  • UI Testing Manual Automated Initial step Design test specification. Create tests. Establish regular runs. Ongoing Click, click, click Analize results File bugs Change the specification Change the tests Qualification High, low for test executors High Effectiveness Low High Other Inexpensive to start Continuous quality monitoring , inexpensive to reuse Fun Bo-o-o-ring Much like programming
  • Continuous build No Yes. Development Success
  • Continuous build with testing No No Yes Yes. = Compilation successful Success Passed
  • Automation approach Record && Replay Coding Test creation Inexpensive* Usually just repeating manual test in special environment Must be accompanied by other means Expensive* Consists of programming Test execution Does not depend on approach Test maintanance Higher (in most cases)* Very much depends on test format Lower* Depends on principles of building test library Test analysis Does not depend on approach (*) Much more information closer to the end of this presentation
  • Jemmy
  • Jemmy v2 Started as a tool to tests TeamWare UI (1999) Used for NetBeans extensions (2000) Official test tool for NetBeans (2001) Open-source (2001) Jemmy v3 Started in (2008) as a proof of concept experiemnt Extended to support JavaFX (2009) Opensource with support of JavaFX 1.2 (2009) Developed in close-source for 1.3 since then
  • Jemmy usages
    • V2 (Swing/AWT)
      • Internal: Swing, NetBeans, Glassfish
      • External:
        • Used by: Boeing (x2), agfa.com, compuware.com, attix5.com, exgate.tek.com, globo.com, gmx.de, non.agilent.com
        • Evaluated by: syntelinc.com, covast.com, visus-tt.com, covast.com, nokia.com, twt.com, ubs.com
    • V3 (FX)
      • Internal: JavaFX, Authoring Tool, JavaStore
  • Demo... Finally!
  • Jemmy v3 Covered in this presentation JavaFX AWT/Swing SWT Scenegraph LCDUI JemmyCore Interfaces AWT robot FX robot Hierarchy Input Scene, node containers Scroller, slider, list, text, ... Generic interfaces
  • UI test Find Do Verify Pass Pass Pass Fail Fail Fail Failure analysis Find next control To perform operation On in Verify that expected State reached Perform necessary actions
  • Lookup
    • By ID
      • Easiest but may not be possible
      • «open_file_btn»
    • By type
      • Most common
      • Button, text, combo box, etc
    • By index
      • Unavoidable
      • 2 nd button with text «browse»
    • By toString()
      • Sucks
      • projectmanager.Main$Main$Script$1Scene$ObjLit$20@4d16318b
    • By text, tooltip, associated label
      • Best, if possible
      • Button with text «browse»
  • UI could be very complicated
  • UI could be very complicated
  • UI could be very complicated
  • Lookup demo
  • Interfaces Interface Control types Description Mouse, Keyboard, Drag Enything Low level input Parent Containers, list (for its content) Something you could look within Selectable Toggle button, radio button, combobox, check box, lists, etc A control which provides limited number of choices CaretOwner Text box, scroll bar, slider A control which has a number value which changes within some range Text Text box Editable text container
  • Interfaces demo
  • Verifications UI feedback Non UI feedback Dialog displayed Test changed Image updated Progress bar changed position File created Database updated Sunset happened :)
  • Waiting
    • UI is a multy-thread environment
    Things happen in background Test code is in another thread
    • Not much could be really verified
    • Everything should be waited for
  • Verification demo
  • Test automation effectiveness
  • E A – automation effectiveness N R and N C are characteristics for a product. T M is a characteristic of a test suite T D and T S depend on test automation approach Smaller T D and T S - higher the E A . T D + * T S N R T M * N R N C * E A = N C *
  • Assumptions: T M = 1 engineer*week T S = 0.1 * T M T D = 5 * T M N R = 8
  • T d or T s – what to minimize T S - if (N C * N R ) is big Multi-platform Compatibility with external products (servers, browsers, ...) Long-living T D - if (N C * N R ) is small Proof of concept Preview
  • Tests fail every now and then ... … because the tested UI is changed
  • Tests fail every now and then ... Ah! And also because errors are made ...
  • End2End demo
  • T s continuends Time spent on What to do %% of time Allocating failures Use test harness 1% - 5% Anderstandint the failure reason Use test logging, save images, save UI state 10% - 80% Fix the tests Move common code to the library ( * ) 90% - 10% (*) The only way it is different from programming is that there are a lot of tests. More on this later.
  • Harness TestNG
  • Understanding failure Logging UI operations Going to push ... button Selecting ... menu UI responces Found list view: … UI hierarchy Scene «…» Group «…» Button «…» UI states Images
  • Demo Jemmy logging functionality
  • Fix the tests One UI, many-many tests. Do as few test code changes as possible Ideally … one change in test code for one change in UI code.
  • Decrease maintenance cost
    • Implement reusable operations in a library
    openFile(String filename)
    • Decrease implementation dependencies
    lookup(Button.class, new ByText<Button>( «Low» ))
    • Increasing stability
    .wrap(0).mouse().click(); Thread.sleep(1000); ...
  • Demo Refining test.
  • Library design approaches
  • Remember the formula? T D + * T S N R T M * N R N C * E A = N C * E A – automation effectiveness To be used for every particular product. N R and N C are unique for a product. T M is a characteristic of a test suite. Smaller T D and T S - higher the E A . Coefficient depend on the way you write your tests
  • T S mainly consists of time for test modification. When product changes, tests need to be changed accordingly. Many tests! Hundreds. “ Less changes of test code per a change in the product UI.” Ideally ... no more than one. But ... how? You are the coders – you know: Move code to test library.
  • Application domain model That's ... car catalog of some sort
  • Application UI
  • Coordinates
    • click(134,32) //selects some record
    • click(215,122) //hits “Properties”
    • sleep(5) //sleeps to let dialog be painted
    • click(64,182) //expands color combo
    • click(235,182) //selects Gray
    • click(235,212) //hit OK
    T d ~= 1.1 * T m , T s ~= 1 * T m Never tried, but ...
  • Widgets
    • Find “Car records” frame
    • Find table
    • Select “1abc234” cell
    • Push “Properties” button
    • Wait for “1abc234” dialog
    • Select “Gray” color in combo box
    • Push “OK”
  • Widgets or coordinates T D ~= 3 * T M , T S ~= .5 * T M
  • UI Primitives
    • Find car list frame
    CarListFrame list = new CarListFrame()
    • Open properties dialog for car “1abc234”
    CarDialog propDialog = list.carProperties(“1abc234”);
    • Set color to gray
    propDialog.setColor(Color.GRAY);
    • Apply changes
    propDialog.ok();
  • T D ~= 5 * T M , T S ~= .2 * T M
  • Domain model
    • Set color to gray for a car “1abc234”
    new CarRecord(“1abc234”). setColor(Color.GRAY); Underneath the cover, CarRecord class does all described earlier
  • T D ~= 7.5 * T M , T S ~= .05 * T M
  • T d and T s together
  • T D and T S for N C =3, N R =8, T M =1
  • E A for N C =3, N R =8
  • Testing JavaFX UI Tips from JavaFX quality team Alexandre (Shura) Iline Java and JavaFX quality architect Oracle
  • Links
    • http://jemmy.dev.java.net