Not a thorough review, but one thing that caught my eye:
TEST_F(NativeBuffer, access_for_read_while_being_read) TEST_F(NativeBuffer, access_for_read_while_being_written) ...etc
The names describe what the arrangement and actions of the test are (while being read, try to read), but not what the expected behavior should be (does not wait). Therefore the names are not as informative as they could be. Perhaps something like:
TEST_F(NativeBuffer, does_not_wait_for_read_access_while_being_read)
« Back to merge proposal
Not a thorough review, but one thing that caught my eye:
TEST_F( NativeBuffer, access_ for_read_ while_being_ read) NativeBuffer, access_ for_read_ while_being_ written)
TEST_F(
...etc
The names describe what the arrangement and actions of the test are (while being read, try to read), but not what the expected behavior should be (does not wait). Therefore the names are not as informative as they could be. Perhaps something like:
TEST_F( NativeBuffer, does_not_ wait_for_ read_access_ while_being_ read)