pull_requests: 173455743
This data as json
id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
173455743 | MDExOlB1bGxSZXF1ZXN0MTczNDU1NzQz | 1972 | closed | 0 | Starter property-based test suite | 12229877 | - [x] Closes #1846 - [x] Tests added - **you bet** - [x] Tests passed - well, the code under test hasn't changed... This is a small property-based test suite, to give two examples of the kinds of tests that we could write for Xarray using Hypothesis. 1. For any array, encoding and decoding it with a CF coder outputs an identical array. As you would hope, these tests pass. 2. For any 2D array, you can call the 2D plotting methods without raising an exception. Alas, this is *not* the case, and Hypothesis will show you the failing inputs (and matplotlib-related tracebacks) to prove it. (Contributing a very small feature to matplotlib was shockingly painful, so I'm not planning to take a similar suite upstream myself unless something changes) Things that I would like to know: - Have I build-wrangled something reasonable here? - Will anyone else contribute property-based tests? I'm happy to help people debug or work out how to test something, but I simply don't have the time to write another test suite for free. - Is this something you *want?* | 2018-03-07T13:45:07Z | 2018-03-20T12:51:28Z | 2018-03-20T12:40:12Z | 2018-03-20T12:40:11Z | 6456df4e9d103a75231d0ea43bb87250ad8745a6 | 0 | 1db77e6060ac4ac91178f8f6dbab845ccb1f80ed | e1dc51572e971567fd3562db0e9f662e3de80898 | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/1972 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests