2
2
Overview
3
3
--------
4
4
5
- The libva- intel-driver uses the Google Test Framework (gtest) for testing the
5
+ The intel-vaapi -driver uses the Google Test Framework (gtest) for testing the
6
6
driver. Documentation for gtest can be found in the test/gtest/doc/
7
7
subdirectory. The original, upstream gtest project can be found at
8
8
https://github.com/google/googletest.
@@ -20,16 +20,16 @@ Google Test Framework Integration
20
20
---------------------------------
21
21
22
22
Google Test recommends it be custom compiled for each project that uses it.
23
- Therefore, the libva- intel-driver project tracks a subset copy of the Google
23
+ Therefore, the intel-vaapi -driver project tracks a subset copy of the Google
24
24
Test Framework source code at release 1.8.0 (initially) in a test/gtest/
25
- subdirectory of the project source tree. The libva- intel-driver copy of gtest
25
+ subdirectory of the project source tree. The intel-vaapi -driver copy of gtest
26
26
will only be updated to new upstream releases (or critical upstream fixes) of
27
27
gtest, only if it is necessary. As of this writing, the last release (1.8.0)
28
28
was August 2016, about three years after its previous release. Thus, there
29
- should be minimal need to update or maintain gtest within the intel-driver
29
+ should be minimal need to update or maintain gtest within the intel-vaapi- driver
30
30
project.
31
31
32
- Libva-intel -driver tests or other project code should *not* be intermixed within
32
+ Intel-vaapi -driver tests or other project code should *not* be intermixed within
33
33
the test/gtest/ subdirectory. The test/gtest/ subdirectory should only contain
34
34
source from the upstream Google Test project to make upgrades simpler.
35
35
@@ -38,8 +38,8 @@ Building Google Test Framework Library
38
38
--------------------------------------
39
39
40
40
The Google Test Framework is compiled as a convenience library (libgtest.la)
41
- within the libva- intel-driver source tree. The rules to build libgtest.la are
42
- maintained in a custom makefile in the libva- intel-driver project tree
41
+ within the intel-vaapi -driver source tree. The rules to build libgtest.la are
42
+ maintained in a custom makefile in the intel-vaapi -driver project tree
43
43
(see test/Makefile.am). The libgtest.la library will be automatically compiled
44
44
if the tests are enabled by configuration.
45
45
@@ -61,7 +61,7 @@ single test/test_i965_drv_video executable. Hence...
61
61
Writing Driver Tests
62
62
--------------------
63
63
64
- Libva-intel -driver tests are defined in the test/ subdirectory using the Google
64
+ Intel-vaapi -driver tests are defined in the test/ subdirectory using the Google
65
65
Test Framework. All driver tests that need a VADriverContextP, VADisplay and
66
66
etc. should define a test fixture that inherits from the I965TestFixture class
67
67
and then use the gtest test fixture macro (TEST_F) to define the test case. The
@@ -141,6 +141,6 @@ these options).
141
141
Distribution
142
142
------------
143
143
144
- A libva- intel-driver source distribution is generated during `make dist` and
144
+ An intel-vaapi -driver source distribution is generated during `make dist` and
145
145
includes the necessary Google Test Framework source code and makefile rules
146
146
along with the driver test source code.
0 commit comments