Changes between Version 5 and Version 6 of EFLWebKitTests

Timestamp:

Jul 16, 2012 1:41:00 AM (12 years ago)

Author:

tmpsantos@gmail.com

Comment:

--

EFLWebKitTests

@@ -50 +50 @@
  * It is recommended to write one test entry at the file per function you are testing (but not enforced). The reason is because every new entry gets a new fixture and consecutively, a fresh webview. We can make sure that a bug on the function A will not interfere on the function B.
  * The test environment can be extended by per-test basis. But in order to do that, you might need to override the test main().
- * Feel free to extend the test fixture and environment if you find a convenience method/function that might be useful for other tests. 
+ * Feel free to extend the test fixture and environment if you find a convenience method/function that might be useful for other tests.
+ * If you are testing a functionality that depends on a feature flag, make sure to wrap your tests around the same flag. Otherwise the test might fail or break the build when the feature is disabled.
 
 == Running the tests ==
@@ -62 +63 @@
  * You should do a total cleanup of the memory allocated by your tests. The reason is because we might use these tests on a future leak detector bot, running them wrapped in valgrind + memchecker (and because this is what nice developers do).
 
+== Disabling the tests ==
+
+ * In case you don't want to build the unit tests, you can disabled them by passing the following arguments to the build script.
+
+{{{
+$ Tools/Scripts/build-webkit --efl --cmakearg="-DSHARED_CORE=ON -DENABLE_API_TESTS=OFF"
+}}}
+
+
 == Questions ==