driver.find_element_by_xpath("//div[contains(@class, 'rankings-list-volume')]").text

I always perform regression testing as soon as the changes come up. The case is the client comes up with changes or additional requirement every now and then and that makes the case more messy. I test something and then the whole things get changed. Again I have to test the changed module and perform integration testing with other modules that is linked with it.

How to deal with such cases?

How many valid equivalent partitions are there?

Theoretically for your range of -100 and 100 there would be three equivalent class partitions:

1. one partition having values below -100 i.e. -101,-102 etc. These are invalid values class.
2. Second partition having values between -100 and 100(including -100 and 100). These are valid values class.
3. Third partition having values greater than 100 i.e. 101,102 etc. These are invalid values class.

Now you can choose one value from each partition. For example,

1. You can choose -118 from first class(invalid class partition).
2. You can choose 70 from second class(valid class partition).
3. You can choose 170 from third class(invalid class partition).

But in my view if you want to check with more values you can do more partitions within class -100 to 100. For example you can divide it into -100 to -51, -50 to 0, 1 to 50, 51 to 100. Then you can choose one value from each of these partitions.

The main purpose of ECP is to reduce the number of test cases(test values) so if you have enough time then you can choose more than one value from each class or you can do make more classes and choose values from them.

1. For which range what are minimum and maximum values?
2. For first class minimum value cannot be described, maximum value is -101.
3. For second class minimum value is -100 and maximum value is 100.
4. For Third class minimum value is 101 and maximum value cannot be described.
5. Using BVA, what values need to be checked for the partitions?

For BVA following values need to be checked:

1. Value immediately below minimum value i.e. -101.
2. Minimum value i.e. -100
3. Value immediately above minimum value of range i.e. -99.
4. value immediately below than maximum value of range i.e. 99
5. Maximum value of range i.e. 100.
6. Value immediately above maximum value of range i.e. 101.

Yes, iOS manual testing is supported in Bitbar Testing (Testdroid). iOS Manual testing was introduced during end of year 2016 and currently it's supported with dedicated devices and Private/Enterprise installations.

For more information http://docs.bitbar.com/testing/user-manuals/manual-testing/ or http://bitbar.com/testing/solutions/public-cloud/

Currently, I'm researching about GUI automated testing on Android and for some reason, I need a tool that can generate code coverage report from manual testing. After a long searching, I found that Jacoco and Emma mention the manual approach on their website. But unfortunately, There is not any up-to-date-working example on the internet.

I have tried a lot of suggesting solution, for example, https://groups.google.com/forum/#!searchin/jacoco/manual$20android|sort:date/jacoco/vx0g_6TKY8Q/0Tg3fX84CAAJ .

It generated a coverage.exec but the file's size was only few byte (of course, Jacoco failed to generate any report from it.)

Here is what I have tried: https://github.com/kindraywind/MyDummy

In app/build.gradle

apply plugin: 'jacoco'
jacoco {
toolVersion ="0.7.8+"  //I did try "0.7.4+" as the suggest.
}

task jacocoTestReport(type: JacocoReport) { … }

In jacoco-agent.properties

destfile=/storage/sdcard/coverage.exec

In app/src/main/AndroidManifest.xml`

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

In MainActivity.java

protected void onStop()
{
super.onStop();
if(BuildConfig.DEBUG)
{
String TAG = "jacoco";
try {
String covPath = Environment.getExternalStorageDirectory().getPath() +     "/coverage.exec";
File coverageFile = new File(covPath);
Class<?> emmaRTClass = Class.forName("com.vladium.emma.rt.RT");
Method dumpCoverageMethod =        emmaRTClass.getMethod("dumpCoverageData",coverageFile.getClass(),     boolean.class, boolean.class);
dumpCoverageMethod.invoke(null, coverageFile, true, false);
} catch (Exception e) {
}

}
}

The emulator is Nexus 5 API 19 (I did try most of the versions.)
The log from device EMMA: runtime coverage data merged into [/storage/sdcard/coverage.exec] {in 8 ms}
The log after run ./gradlew jacocoTestReport Unable to read execution data file /Users/MyDummy/app/coverage.exec
I'm using OSX10.12.3 if it related.

To sum up, I need to know (or any working example) how to obtain code coverage while:

Test the app manually.
On Android application.
Which is using Gradle not Maven or Ant.
Android Studio not Eclipse.
I see no way out and would really appreciate a help.

In my opinion: A test scenario is functionality that can be tested. Something that the user may want to do with your system and you want to verify. A scenario can have one or more test case. A test case is a formal definition of a test. It defines prerequisites, an action, and the expected result. A test suite is a set of test cases which are logically connected. Eg: test cases which test the same functionality of an app. A test plan is plan how you want to execute your tests to reach your desired test coverage. It's a project document and deals with questions like: which suites should be run in all development iterations. Which should be run on releases. Who is responsible for functional testing, who is for non-functional tests. What kind of resources are needed. When will be the different tests executed...

Is your QA Team effective. I am finding that many QA people that I have encountered are more verifiers and software breaking experts.

What I mean by verifiers is, they step through all scenarios provided, basically walking through the application and ensuring that it does what is supposed to.

What I mean by breakers is, they verify but they also diligently seek out scenarios that break the software and uncover defects.

Are your findings similar?

Of historical note on breaking software There was a team inside IBM in the 80's called the Black Team. They had a culture of saying that they had "succeeded" when they broke the software to encourage the identification of defects. They considered their work a "failure" when they failed to find/identify any faults in the software. On the other hand, the outcome of their "failure" was great reliable software...

And the book: "How to Break Software: A Practical Guide to Testing" by James Whittaker

I figured out what the problem was. Indeed, the element I was looking for associated frame, and the webdriver was looking for elements in the root of the html page. From this it turns out that the Selenium IDE sees at once the entire structure of the page and, accordingly, all the elements. This is probably why the problem did not arise before. As a result, this is solved by switching to the desired frame via the command:

driver.switchTo (). Frame (driver.findElement (By.id ("here is the frame id")));

Good day to all! I switched from Selenium IDE to WebDriver + JUnit and I have the following problem: locators, which Selenium IDE saw before, does not see WebDriver. For example:

IDE command

waitForVisible -> xpath =. // * [@ id = 'listContainer']

The element is being discovered.

Command from JUnit:

1.Assert.assertTrue ("Element isn't exist",! Driver.findElements (By.xpath (".//* [@ id = 'listContainer']")). IsEmpty ());

Error: Element isn't exist

or

If you try to find by id

2.Assert.assertTrue (driver.findElement (By.id ("listContainer")). IsDisplayed ());
Error: NoSuchElementException: Unable to locate element ...

Note:

The timer is on and the elements on the page are loaded.

Full code below:

public class Simpletest {
String baseUrl;
WebDriver driver;
    @Before
    public void testSetup () {
        driver = new ChromeDriver ();
        baseUrl = "http://127.0.0.1:8000";
    }

    @After
    public void testShutDown () {
        driver.close ();
    }

    @Test
    public void shouldHaveTestAboutProfileSettings () {

        driver.get (baseUrl + "/SIMULATOR/index.html");
        wait (2);
    // Assert.assertTrue ("Element isn't exist",! Driver.findElements (By.xpath (".//* [@ id = 'listContainer']")). IsEmpty ());
       Assert.assertTrue (driver.findElement (By.id ("listContainer")). IsDisplayed ());

    }

  public void wait (int seconds) {
  try {
      Thread.sleep (seconds * 1000);
  } catch (InterruptedException e) {
      e.printStackTrace ();
  }
 }
}

HTML: HTML

Ideally, I need to check for the presence of a clickItem with id = 0