You could alternatively do: driver.findElements(By.id(“…”)).size() != 0 Which saves the nasty try/catch P.S.: Or more precisely by @JanHrcek here !driver.findElements(By.id(“…”)).isEmpty()
android.jar contains only stub implementation of the classes. It provides the means for you app to build, once you have your APK you must run it on an android device or emulator. If I’m not wrong you are trying to run on host’s JVM.
One thing to also remember, there’s nothing stopping you from writing functions to avoid the boilerplate. For example I have a command line app that uses log and I wrote this function: func captureOutput(f func()) string { var buf bytes.Buffer log.SetOutput(&buf) f() log.SetOutput(os.Stderr) return buf.String() } Then used it like this: output := captureOutput(func() { … Read more
iPhone OS 4.0 (just announced) includes a “UIAutomation Instrument” for test automation. Automated testing Automate the testing of your application by scripting touch events using the new UIAutomation Instrument. From: http://developer.apple.com/technologies/iphone/whats-new.html#tools
You can expose the test classes via a ‘tests’ configuration and then define a testCompile dependency on that configuration. I have this block for all java projects, which jars all test code: task testJar(type: Jar, dependsOn: testClasses) { baseName = “test-${project.archivesBaseName}” from sourceSets.test.output } configurations { tests } artifacts { tests testJar } Then when … Read more
Contrary to the much-voted-up answer that @dlev gave, it can sometimes be very useful/needful to write a test like you’re suggesting. The public API of a class, as expressed through its interface, is the most important thing to test. That being said, I would use neither of the approaches you mentioned, but a Parameterized test … Read more
My preference is to have classes that use time actually rely on an interface, such as interface IClock { DateTime Now { get; } } With a concrete implementation class SystemClock: IClock { DateTime Now { get { return DateTime.Now; } } } Then if you want, you can provide any other kind of clock … Read more
Do not use multiple inheritance, it will bite you later. Instead you can just move your base class into the separate module or wrap it with the blank class: class BaseTestCases: class BaseTest(unittest.TestCase): def testCommon(self): print(‘Calling BaseTest:testCommon’) value = 5 self.assertEqual(value, 5) class SubTest1(BaseTestCases.BaseTest): def testSub1(self): print(‘Calling SubTest1:testSub1’) sub = 3 self.assertEqual(sub, 3) class SubTest2(BaseTestCases.BaseTest): … Read more
Here is my fancy version: import org.gradle.api.tasks.testing.logging.TestExceptionFormat import org.gradle.api.tasks.testing.logging.TestLogEvent tasks.withType(Test) { testLogging { // set options for log level LIFECYCLE events TestLogEvent.FAILED, TestLogEvent.PASSED, TestLogEvent.SKIPPED, TestLogEvent.STANDARD_OUT exceptionFormat TestExceptionFormat.FULL showExceptions true showCauses true showStackTraces true // set options for log level DEBUG and INFO debug { events TestLogEvent.STARTED, TestLogEvent.FAILED, TestLogEvent.PASSED, TestLogEvent.SKIPPED, TestLogEvent.STANDARD_ERROR, TestLogEvent.STANDARD_OUT exceptionFormat TestExceptionFormat.FULL } info.events … Read more
Try using an anonymous function instead: expect( function(){ parser.parse(raw); } ).toThrow(new Error(“Parsing is not possible”)); you should be passing a function into the expect(…) call. Your incorrect code: // incorrect: expect(parser.parse(raw)).toThrow(new Error(“Parsing is not possible”)); is trying to actually call parser.parse(raw) in an attempt to pass the result into expect(…),