Shift Instrumentation test written in Unit Test directory for AdministratorControlsFragmentTest
See original GitHub issueDescribe the bug
There are some test cases written in src/test/java/org/oppia/android/app/testing/administratorcontrols/AdministratorControlsFragmentTest.kt
which are instrumentation test but the file exist in unit test folder. (i.e. app/src/test)
Expected behavior Look for the instrumentation tests in this file and shift them to the instrumentation test directory (i.e. app/src/sharedTest).
Additional context How to test on Espresso?
How to send a Pull Request for this Issue Add screenshot showing shifted tests are passing on Espresso.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Advanced test setup - Android Developers
Advanced test setups. ... Configure instrumentation manifest settings; Change the test build ... Encapsulates options for local unit tests.
Read more >Developing Android unit and instrumentation tests - Tutorial
This tutorial describes how to write unit and instrumentation tests for your Android application. It describes how to execute these tests via Android...
Read more >Configure unit tests by using a .runsettings file - Microsoft Learn
Run the unit tests to use the custom run settings. ... Select test solution-wide runsettings file menu in Visual Studio ...
Read more >Android Studio unit testing: read data (input) file - Stack Overflow
Put unit test classes in java directory and put your resources file ... Run unit test by Ctrl + Shift + F10 on...
Read more >iOS Unit Testing and UI Testing Tutorial - RayWenderlich.com
What do you need to test? If your goal is to extend an existing app, you should first write tests for any component...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@anandwana001 Can I work on this?
FYI: I updated the main comment to reference the relevant directories for where the Espresso tests should go to ensure there isn’t any potential confusion that these tests should go under instrumentation/.