ui-testing

I have a test for a collection view that works like this: func testDeleteItem() { app.collectionViews.staticTexts["Item"].tap() app.buttons["Delete"].tap() XCTAssertEqual(app.collectionViews.cells.count, 2) XCTAssertFalse(app.collectionViews.cells.staticTexts["Item"].exists) } After the tap, there is a new screen with the delete button. When the button is tapped, the screen dismisses itself and reloads the collection view. Everything goes as expected in the UI, but I get both asserts failing. In the first count it is still 3 and in the second item it still exists. I have found the solution,

I have ListView with pictures and text. When I try to click item, I get error android.support.test.espresso.AmbiguousViewMatcherException: 'with id: com.cifrasoft.telefm:id/cardsGridView' matches multiple views in the hierarchy. Problem views are marked with '****MATCHES****' below. I use the following code: onData(hasToString(startsWith("Item Text"))) .inAdapterView(withId(R.id.cardsGridView)) .perform(click()); Can I click ListView using position of Adapter , without matches or startWith ? Try with atPosition(). e.g. onData(hasToString(startsWith("Item Text"))) .inAdapterView(withId(R.id

I have an application that makes use of core data. The behavior of the application is different depending on whether that data has been populated yet. I had hoped that, before each test case, the core data would be emptied, making each test case run on a fresh app instance. Test cases shouldn't depend some test device's state, especially because other test cases manipulate this state. Unfortunately, by default, the core data lingers not only between test cases, but also between completely separate test runs. I'm trying to fix this behavior. My first idea was to dump all core data in the

I'm struggling to get Robotium to work on the gradle-based Android Studio and I can't find the way to do it This is my build.gradle file buildscript { dependencies { repositories { mavenCentral() mavenLocal() } classpath 'com.android.tools.build:gradle:0.5.+' } } apply plugin: 'android' repositories { mavenCentral() /* maven { url "https://oss.sonatype.org/content/repositories/snapshots" }*/ } sourceSets { testLocal { java.srcDir file('src/test/java') resources.srcDir file('src/test/resources') } } android { compileSdkVersion 17 buildToolsVersion "17.0.0" defaultConfig { minSdkVersion 15

I just wanted some opinions from people that have run Selenium ( http://selenium.openqa.org ) I have had a lot of experience with WaTiN and even wrote a recording suite for it. I had it producing some well-structured code but being only maintained by me it seems my company all but abandoned it. If you have run selenium have you had a lot of success? I will be using .NET 3.5, does Selenium work well with it? Is the code produced clean or simply a list of all the interaction? ( http://blogs.conchango.com/richardgriffin/archive/2006/11/14/Testing-Design-Pattern-for-using-WATiR_2F00_N.aspx ) How

Is there a way to automatically generate IDs on SWT-Widgets so UI-Tests can reference them? I know i can manually set an id using seData but I want to implement this feature for an existing application in a somewhat generic fashion. You can recursively assign IDs for all your shells in your application using Display.getCurrent().getShells(); and Widget.setData(); . Setting the IDs Shell []shells = Display.getCurrent().getShells(); for(Shell obj : shells) { setIds(obj); } You have access to all the active (not disposed) Shells in your application with the method Display.getCurrent().getShells()