[Test Fixit] Code coverage test example.

client/site_tests/example_UnitTest/src/Makefile

+# Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+TARGET = unit_test
+OBJECTS = main.o
+INCLUDES = -I$(GCLIENT_ROOT)/src/common
+OPTIONS = -fprofile-arcs -ftest-coverage -fno-inline -O0
+LIBS = -lgtest
+PACKAGES = 
+
+all: $(TARGET)
+
+$(TARGET): $(OBJECTS)

[kmixter1, 2010/04/09 22:07:23]

As Darin mentioned, our current thinking on how to do unit testing, which mostly
dovetails well with this CL, is:
a) you add to the ebuild a feature/use flag to indicate you want to build unit
tests
b) it builds and installs those unit tests which must be gtest-harness tests
into %SYSROOT%/usr/local/unittests
c) installing the image (specifically the stateful partition) puts them on the
device
d) an autotest finds them all and runs them and reports their results

we could put both gcov/instrumented gtest executables and regular ones there,
though probably we'd want to just have all unit tests be gcov/instrumented. 
Which means, we could pretty much parameterize your UnitTest classes to take
executable names and have a control file that finds all the tests and runs them
as separate autotest tags.

In any case, that part's not built yet, so this is a good example to start with.

+        $(CXX) $(CXXFLAGS) $(OPTIONS) $(LDFLAGS) $(PACKAGES) $(OBJECTS) $(LIBS) \
+                        -o $(TARGET)
+        
+-include $(OBJS:.o=.d)
+
+.cc.o:
+        $(CXX) $(CXXFLAGS) $(PACKAGES) $(OPTIONS) $(INCLUDES) -c $< -o $@
+        $(CXX) -MM $(CXXFLAGS) $(PACKAGES) $(OPTIONS) $(INCLUDES) $< > $*.d
+        @mv -f $*.d $*.d.tmp
+        @sed -e 's|.*:|$*.o|' < $*.d.tmp > $*.d
+        @sed -e 's/.*://' -e 's/\\$$//' < $*.d.tmp | fmt -l | \
+                        sed -e 's/^ *//' -e 's/$$/:/' >> $*.d
+        @rm -f $*.d.tmp
+        
+clean:
+        $(RM) *.o *.d $(TARGET)
+