Current execution patterns unit tests are policy driven, which means that all of the range policy tests for parallel_for, parallel_reduce, parallel_scan are all part of the same suite of tests. Same goes for MDRangePolicy and TeamPolicy.
Also, the ViewValueFunctor used to initialize the contents of a view has a dependency on the ParallelFor implementation within the execution/memory space. Because of this dependency, the parallel_for tests need to be independent of the Kokkos::View.
For incremental Execution Space development, individual tests are needed for parallel_for - RangePolicy and parallel_for - MDRangePolicy that are not dependent on Kokkos::View
parallel_reduce is needed as well.
Because there aren't any dependencies on parallel_scan, this one may be deferred to the larger unit tests.
Current execution patterns unit tests are policy driven, which means that all of the range policy tests for parallel_for, parallel_reduce, parallel_scan are all part of the same suite of tests. Same goes for MDRangePolicy and TeamPolicy.
Also, the ViewValueFunctor used to initialize the contents of a view has a dependency on the ParallelFor implementation within the execution/memory space. Because of this dependency, the parallel_for tests need to be independent of the Kokkos::View.
For incremental Execution Space development, individual tests are needed for parallel_for - RangePolicy and parallel_for - MDRangePolicy that are not dependent on Kokkos::View
parallel_reduce is needed as well.
Because there aren't any dependencies on parallel_scan, this one may be deferred to the larger unit tests.