Module redvox.tests.common.test_sensor_reader_utils

tests for loading sensor data

"""
tests for loading sensor data
"""
import unittest

import pyarrow as pa
import numpy as np

from redvox.common.sensor_data import SensorType
from redvox.common import sensor_reader_utils as sdru


class EmptySensorTest(unittest.TestCase):
    def test_empty_sensor(self):
        empty_sensor = sdru.get_empty_sensor("empty")
        self.assertEqual(empty_sensor.num_samples(), 0)
        self.assertTrue(np.isnan(empty_sensor.sample_rate_hz()))
        self.assertEqual(empty_sensor.type().value, SensorType.UNKNOWN_SENSOR.value)


class SampleStatisticsTest(unittest.TestCase):
    def test_sample_stats(self):
        new_df = pa.Table.from_pydict({"timestamps": [10000, 20000, 30000, 40000, 50000]})
        rate, interval, intvl_std = sdru.get_sample_statistics(new_df)
        self.assertEqual(rate, 1e2)
        self.assertEqual(interval, 1e-2)
        self.assertEqual(intvl_std, 0)

Classes

class EmptySensorTest (methodName='runTest')

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named 'runTest'.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test's environment ('fixture') can be implemented by overriding the 'setUp' and 'tearDown' methods respectively.

If it is necessary to override the init method, the base class init method must always be called. It is important that subclasses should not change the signature of their init method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when the instance's assertion methods fail; test methods raising this exception will be deemed to have 'failed' rather than 'errored'. * longMessage: determines whether long messages (including repr of objects used in assert methods) will be printed on failure in addition to any explicit message passed. * maxDiff: sets the maximum length of a diff in failure messages by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

Create an instance of the class that will use the named test method when executed. Raises a ValueError if the instance does not have a method with the specified name.

Expand source code

class EmptySensorTest(unittest.TestCase):
    def test_empty_sensor(self):
        empty_sensor = sdru.get_empty_sensor("empty")
        self.assertEqual(empty_sensor.num_samples(), 0)
        self.assertTrue(np.isnan(empty_sensor.sample_rate_hz()))
        self.assertEqual(empty_sensor.type().value, SensorType.UNKNOWN_SENSOR.value)

Ancestors

• unittest.case.TestCase

Methods

def test_empty_sensor(self)

Expand source code

def test_empty_sensor(self):
    empty_sensor = sdru.get_empty_sensor("empty")
    self.assertEqual(empty_sensor.num_samples(), 0)
    self.assertTrue(np.isnan(empty_sensor.sample_rate_hz()))
    self.assertEqual(empty_sensor.type().value, SensorType.UNKNOWN_SENSOR.value)

class SampleStatisticsTest (methodName='runTest')

A class whose instances are single test cases.

By default, the test code itself should be placed in a method named 'runTest'.

If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.

Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test's environment ('fixture') can be implemented by overriding the 'setUp' and 'tearDown' methods respectively.

If it is necessary to override the init method, the base class init method must always be called. It is important that subclasses should not change the signature of their init method, since instances of the classes are instantiated automatically by parts of the framework in order to be run.

When subclassing TestCase, you can set these attributes: * failureException: determines which exception will be raised when the instance's assertion methods fail; test methods raising this exception will be deemed to have 'failed' rather than 'errored'. * longMessage: determines whether long messages (including repr of objects used in assert methods) will be printed on failure in addition to any explicit message passed. * maxDiff: sets the maximum length of a diff in failure messages by assert methods using difflib. It is looked up as an instance attribute so can be configured by individual tests if required.

Create an instance of the class that will use the named test method when executed. Raises a ValueError if the instance does not have a method with the specified name.

Expand source code

class SampleStatisticsTest(unittest.TestCase):
    def test_sample_stats(self):
        new_df = pa.Table.from_pydict({"timestamps": [10000, 20000, 30000, 40000, 50000]})
        rate, interval, intvl_std = sdru.get_sample_statistics(new_df)
        self.assertEqual(rate, 1e2)
        self.assertEqual(interval, 1e-2)
        self.assertEqual(intvl_std, 0)

Ancestors

• unittest.case.TestCase

Methods

def test_sample_stats(self)

Expand source code

def test_sample_stats(self):
    new_df = pa.Table.from_pydict({"timestamps": [10000, 20000, 30000, 40000, 50000]})
    rate, interval, intvl_std = sdru.get_sample_statistics(new_df)
    self.assertEqual(rate, 1e2)
    self.assertEqual(interval, 1e-2)
    self.assertEqual(intvl_std, 0)