Add tests for settings and sortingAndGrouping module

[GOVINDDIXIT]

This PR is specific to GSoC'19 project (Improve test automation in Rocket.Chat Android Repo)

Change Log

• Add UI Automator for cross-app functional UI testing
• Add Unit tests for the settings module
• Add UI test for the settings module
• Add UI test for sortingAndGrouping module
• Remove run UI test script from CircleCi

Current Code coverage: 35% by Instructions 19% by branch

[codecov]

Codecov Report

Merging #12 into develop will increase coverage by 0.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             develop     #12      +/-   ##
============================================
+ Coverage       0.51%   0.67%   +0.16%     
- Complexity        25      32       +7     
============================================
  Files            321     321              
  Lines          10456   10456              
  Branches        1821    1821              
============================================
+ Hits              54      71      +17     
+ Misses         10382   10364      -18     
- Partials          20      21       +1

Impacted Files	Coverage Δ	Complexity Δ
app/src/main/java/testConfig/Config.kt	0% <ø> (ø)	0 <0> (ø)	⬇️
...android/settings/presentation/SettingsPresenter.kt	24.28% <0%> (+24.28%)	7% <0%> (+7%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 872f900...0cc0eee. Read the comment docs.

[ear-dev]

Are you counting on this to throw an exception if the user is already logged in? Is that safe? Is it guaranteed that no other exception could be thrown? I just wonder if there is a more positive test whether the user is logged in...

[GOVINDDIXIT]

The logic here is that if the user is already logged in then there will be a NoMatchingViewException which will be caught and for which we have to do nothing just proceed further in this case navigateToChannelDetails but if the user is not logged in then we have to make the user login first then navigate further

[GOVINDDIXIT]

I have to place this logic in some tests because the tests should be independent of each other (best practices) Also it saves tests from failing, there can be a case in which a test which tests a scenario after user authentication is performed before the actual login of the app as the there is no predefined order in which test run. So, in that case, it will perform login first and then test the required thing

[ear-dev]

Govind...... I tested the latest, and all tests passed except the two appStore tests. I'm pretty sure that is because the appStore does not recognize my emulator as a compatible device for the RocketChat app, so it does not offer the "rate" and "feedback" options. Have you seen this issue? I have tried to debug, but still have no idea what might be missing.

I am inclined to approve this PR, but first, can you point me to the code you added that protected other tests from failing in the case of a test failure? I'm curious...... thanks.

[GOVINDDIXIT]

Govind...... I tested the latest, and all tests passed except the two appStore tests. I'm pretty sure that is because the appStore does not recognize my emulator as a compatible device for the RocketChat app, so it does not offer the "rate" and "feedback" options. Have you seen this issue? I have tried to debug, but still have no idea what might be missing.

I am inclined to approve this PR, but first, can you point me to the code you added that protected other tests from failing in the case of a test failure? I'm curious...... thanks.

Thanks @ear-dev. Yes, the compatibility issue of the emulator seems to be the cause of the failure at first look. But when I dig into it I found that in some cases the intent to open the Gmail and play store is taking more time than expected. Since I am checking whether the Rocket.Chat text is present in the display screen when the play store opens up. It fails when it takes more time to open the play store app, same is with the Gmail app. I also have an incompatible emulator Still the tests are passing 8/10 times failing 2 times because of intent taking more time. As discussed I will unit test these two test cases.

[GOVINDDIXIT]

I am inclined to approve this PR, but first, can you point me to the code you added that protected other tests from failing in the case of a test failure? I'm curious...... thanks.

previously tests were failing because the instance of play store and Gmail already open causing UI hindrance to other tests. Earlier I was using pressBack() which is a method from Espresso to press back button, But I should use mDevice.pressBack() because we are using UI Automator here which is used to test interaction outside the app or bw multi apps. So mDevice.pressBack() works in this case and now these instances of open apps(play store and gmail) will not affect our test flow.