search

rahul7386 / robotium

Automatically exported from code.google.com/p/robotium
0 stars 0 forks source link

Solo not gettin initiated after opening other Activity #603

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
   1. Run two tests for an application
   2. The first test starts a function which opens another application 
      (for example writing a message, opening a picture or the browser)
   3. When the first test is finished, the second test is only getting to   the setUp() method and is not creating a new Solo (the test is doing nothing and only finishes when I stop the test manually)

What is the expected output? What do you see instead?

   I expect a normal test run (especially when both tests test the same activity)

What version of the product are you using? On what operating system?

   Android: 4.0.2 (Emulator)
   Robotium: 5.0.1

Please provide any additional information below.

  This problem accures everytime and even if I run one test two times with a test suite. (The first test succeeds and opens the browser and the second test
does start but is doing nothing since it hangs up at the point where Solo gets 
instantiated)

Thank you very much for your time!

Original issue reported on code.google.com by reneprei...@gmail.com on 8 May 2014 at 1:48

GoogleCodeExporter commented 9 years ago 
Please use finishOpenedActivities in your tearDown.

Original comment by renasr...@gmail.com on 9 May 2014 at 11:35