Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 438022 - iOS toolkit - known issue: CAPs which internally make use of KIF
Summary: iOS toolkit - known issue: CAPs which internally make use of KIF
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: RC (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 437056
  Show dependency tree
 
Reported: 2014-06-24 07:09 EDT by Markus Tiede CLA
Modified: 2016-05-31 09:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Tiede CLA 2014-06-24 07:09:42 EDT
CAPs which internally make use of KIF
 - take approx. 2-3 seconds
 - cause log output in the AUT
 - only have non-specific failure information
 - sometimes do not work in AUTs (unkown selectore sent to instance...)
 - sometimes do nothing e.g. when the widget being "addressed" in the test is not the one which is reacting to specific events - e.g. the label of a button instead of the button itself
Comment 1 Alexandra Schladebeck CLA 2014-06-30 11:09:38 EDT
Markus, which CAPs are affected? All of them? Just certain ones?
Comment 2 Markus Tiede CLA 2014-07-02 05:23:06 EDT
All CAPs that are not "checking" / synchronizing states / properties of widgets are / might be affected of this (maybe even multiple times) e.g. a "Component with text input - replace text" internally uses the following structure:
 -* tap component
 - select all (via API)
 -* type characters on keyboard

I've marked the internal steps of that CAP using KIF with * - as a rule of thumb you can say: whenever a remote controlling robot is used KIF is in use.
Comment 3 Marvin Mueller CLA 2016-05-31 09:14:49 EDT
We have dropped support for the iOS Toolkit