Conference Notes and Best Practices Release 1.3 ... - Read the Docs

More documents

Recommendations

Info

Conference Notes and Best Practices, Release 1.3 Building Search • Model attribute • Templates • Field method (Method that refers to a field) • Queryset to define a search index (Specify what gets added to the index) Help Users • Improve quality of search • Adjust relevance • Boot fields, documents, terms • Log searches, results, and their success • Use search engine as cache Doing More with Search • ElasticSearch can configure index analysis. • Can configure tokenizers and filters • Write a custom backend/New Default analyzer/Update search mapping Some Gotchas • Don’t index fields used for sorting • Debug search issues (Is this plugged in, is anything indexed?) • Haystack debug pannel for django debug toolbar SearchIndex = data mapping Writing Fast and Efficient Unit Tests For Django Presenter: Casey Kinsey Track: I Description: Many developers have difficulty finding clear guidelines and best practices for how to test efficiently, leading to a flimsy, slow, and ineffective test suite. This talk will cover some basic (but oft overlooked) principles of unit and integration testing, and dive into more advanced topics such as testing with read only data and using Mock ultra-focused and fast testing. Writing Faster Tests A real need for test speed • Made an initial production release of a real product for a national media company • Test Coverage not great 30 Chapter 3. Conferences
Conference Notes and Best Practices, Release 1.3 • Started seeing regressions • Aggressively pursue greater test coverage • Results were successful, but needed faster tests. Should I be concerned? • You probably have lots of tests • You probably run them frequently • Slow tests will cause developers to stop running them • Preparing code for integration becomes painful • Deployment speed is directly affected How to write better tests • Many project suites are comprised of integration tests • Write unit tests • Unit test calls a small “unit” of code • Integration tests, test the contracts between the units • Using the django test client is a giveaway that its an integration test. • Write unit tests that are very limited in functionality/scope Unit Vs Integration • For each function that contains business logic, there should be a unit test • for each page/view/user path of your project there should exist an integration test. • Setup tests Set up tests cautiously • Be judicious about how you use setUp/tearDown • Think like middleware. Do I really need this for every test in this case? • One inefficient computation can cripple the whole test case. • Add @classmethod. very effective for read only data. Data will persist between tests! The Database is Hot Lava • If you touch it, you will die • Not really, but its one of the slowest things your application will do in a unit test. • Work with read only, non persisted data. • Use in memory model instances model = ModelName(attribute=x) • Avoid fixtures 3.1. Django Con US 2013 31
Page 1: Conference Notes and Best Practices
Page 5 and 6: Conference Notes and Best Practices
Page 7 and 8: CHAPTER 1 Meetups 1.1 Django Deploy
Page 13 and 14: CHAPTER 2 Notes 2.1 Django Resource
Page 17 and 18: CHAPTER 3 Conferences 3.1 Django Co
Page 33: Conference Notes and Best Practices
Page 85 and 86:
Conference Notes and Best Practices
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
show all

Conference Notes and Best Practices Release 1.3 ... - Read the Docs

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?