Databases
StackOverflow2013
Postsdbo
POHow to test specific hardware features with Robolectric on android?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to test specific hardware features with Robolectric on android?
    primarykey
    data
    text
    <p>I started writing a robolectric test around hardware specific features, like sensors and camera (front and back).</p> <p>Imagine this class:</p> <pre><code>class CheckHardware { private bolean hasCamera(Context context) { PackageManager pm = context.callingActivityContext .getPackageManager(); // camera support Boolean frontCam = pm.hasSystemFeature("android.hardware.camera.front"); Boolean rearCam = pm.hasSystemFeature(PackageManager.FEATURE_CAMERA); if (frontCam || rearCam) { return true; } return false; } } </code></pre> <p>So i want to test different scenarios where there is a front camera and a rear camera, only a front camera or no camera at all. In my app its a bit more complicated but hope this makes it easier to understand what i mean.</p> <p>For now i did it like this, which feels a bit odd.</p> <pre><code>RobolectricPackageManager pm = (RobolectricPackageManager) Robolectric.application.getPackageManager(); pm.setSystemFeature(PackageManager.FEATURE_CAMERA, true); </code></pre> <p>I thought about writing my own test runner, so for all expected hardware settings a specific runner like this</p> <pre><code>public class WithCameraTestRunner extends RobolectricTestRunner { @Override public void setupApplicationstate(RobolectricConfig robolectricConfig) { super.setupApplicationState(robolectricConfig); ShadowApplication shadowApplication = shadowOf(Robolectric.application); shadowApplication.setPackageName(robolectricConfig.getPackageName()); RobolectricPackageManager pm = new RobolectricPackageManager(Robolectric.application, robolectricConfig) pm.setSystemFeature(PackageManager.FEATURE_CAMERA, true); shadowApplication.setPackageManager(pm); } } </code></pre> <p>Not quite happy with that either as i want to test different scenarios in the same test.</p> <p>Any ideas? Whats the best approach for this?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTosa
    1. USTosa
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to test specific hardware features with Robolectric on android?
      1. USTosa
      1. VTBountyStart
    2. VO
      singulars
      1. POHow to test specific hardware features with Robolectric on android?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to test specific hardware features with Robolectric on android?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCould you describe more detailed which functionality you want to test?
      singulars
      1. POHow to test specific hardware features with Robolectric on android?
      1. USEugen Martynov
    2. COIts not so much about what exactly i want to test, i want to test something which has different behavior when the device has a camera or there is nfc. It could be as easy as a class has a method which checks for the camera and includes some logic which i want to test.
      singulars
      1. POHow to test specific hardware features with Robolectric on android?
      1. USTosa
    3. COupdated my question with a example class
      singulars
      1. POHow to test specific hardware features with Robolectric on android?
      1. USTosa
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload