Chris Jones committed d21d5ea


Comments (0)

Files changed (1)


     Dealing with cache
         Cache should be agnostic to model changes.
         Version objects in cache.
+    TDD
+        Goes against prototyping
+ - Make a game out of testing
+    Test driven refactoring
+        Almost guarenteed that you will be rafactoring
+    Successful strategies
+        Require unit tests for all code going forward
+        Establish a good foundation to build on
+    Every bug is two bugs
+        One in the code that broke and one in the test that failed to catch it
+    Tests need data
+        Fixtures
+            user types/permissions, relatively constant stuff
+        Use ObjectCreator
+            frequently changing objects
+    Should I get test data from cache?
+        NO
+    Test infrastructure
+        If you have servers like Solr or RabbitMQ
+            Run them on staging not in the dev
+        Leverage logging where useful
+    Testing tools:
+        Nose
+        Coverage
+        Mock
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.