response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this test 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses events via SSE or WebSockets. • ...And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this test 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses events via SSE or WebSockets. • ...And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this test 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses events via SSE or WebSockets. • ...And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this test 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses events via SSE or WebSockets. • ...And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this test 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses events via SSE or WebSockets. • ...And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this test 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses events via SSE or WebSockets. • ...And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses upload events via SSE or WebSockets. …And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses upload events via SSE or WebSockets. …And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses upload events via SSE or WebSockets. …And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into

response.status == falcon.HTTP_CREATED assert call().write(fake_image_bytes) in mock_file_open.mock_calls assert response.headers['location'] == '/images/{}.png'.format(fake_uuid) As you can see, this 'image/png') == fake_uuid + '.png' assert call().write(fake_image_bytes) in mock_file_open.mock_calls Now give it a try: $ pytest tests -k test_saving_image Like the former test, this one still uses upload events via SSE or WebSockets. …And much more (patches welcome, as they say)! Compared to the sync version, asynchronous code can at times be harder to design and reason about. Should you run into