Blitz provides some basic testing utilities in the generatedtest/utils.tsx file. These are intended for use with Vitest and ReactTesting Library to allow advanced configuration for your testingenvironment. Customizing this file can be useful for testing things likeglobal providers as well as certain parts of your app which Blitz handlesinternally such as routing and data querying.
dehydratedState - The server state passed along to the applicationcontaining the results of server-side queries. Useful for testingqueries that need to beprerendered in markup and hydrated on the client.
If you plan to integrate it into your Blitz application, you can look atourexample with a Cypress setup.It includes a simple factory pattern, a command for creating and loggingin a user, and a few example tests.
I have a Ubuntu 14.04 server setup with NGINX, HHVM, PHP5-FPM (as a backup), Percona MySQL, Memcached (which will be replaced by Redis). I have fastcgi_cache setup for WordPress and object caching done over memcached. All cool and dandy in theory, but not in practice.
The Rainbow Six Siege test server currently offers an early look at the new features of Operation Chimera, as well as some balance changes for existing operators. Some of the biggest changes involved a major buff for Blitz, but after some early feedback the developers are pulling back on his power.
Legacy online IDEs run your entire dev environment on a remote server and stream the results back across the internet to your browser. The problem with this approach is that it yields few security benefits and provides a worse experience than your local machine in nearly every way: it takes minutes to spin up containers, is prone to network latency, cannot work offline, often results in network timeouts, debugging frozen/broken containers is nearly impossible, and hitting refresh just reconnects you to the broken container again.
  This tutorial describes a prototype feature. Prototype features are typically not available as part of binary distributions like PyPI or Conda, except sometimes behind run-time flags, and are at an early stage for feedback and testing.
I've tuned indexes in the past, but on tables with relatively few sp's. This table has been identified as a problem but nobody's clear how to effectively test hundreds of dependent sp's. I believe I'll have to run every stored procedure, repeatedly, both before and after indexing, to demonstrate that any change is useful.
I've seen load-testing tools, and that inspired my first plan of attack. Is there an open-source tool that analyses the code / table and provides meaningful parameters, then executes hundreds of sp's in independent loops, multi-threaded? I hope not to have to hand-curate the parameter values. The server is rebooted weekly so historical patterns take a while to collect.
The default "auto" setting enables showing changes as user types, which may provide a nice reactive feel to project demos. However, this also means that the development server or compiler used in the project may receive invalid code before the user finished typing. Since not all dev servers and compilers are resilient to invalid input, you may want to set compileTrigger to "save" instead to limit errors.
df19127ead