Speeding Up Siesta – Sandboxing Now Optional
Sandboxing – what is it exactly..?
Every since the first Siesta release, tests have always been executed in their own iframes – “sandboxed”. This feature of Siesta assures that tests get a fresh context as they start and can’t interfere with other tests by changing global browser properties or defining global variables. Another big bonus is that you don’t need to manually clean up after your tests. As a sandboxed …
Code coverage with Siesta 2.0
Siesta 2.0 was released last week during SenchaCon 2013 in Florida. The main features of this release are the brand new UI (based on Ext JS 4.2) and the ability to generate code coverage reports. Code coverage is a big and exciting addition that was frequently requested in the past year, and we already use it ourselves internally. Since we think there might a few additional features left …
Road to Ext Scheduler v2.2: Overrides
We’re currently busy finalizing a major refactoring of our Ext Scheduler component which will be released as v2.2. There are two major reasons for this refactoring. First of all we needed to refactor to enable certain pieces of the core functionality to be shared with our Touch Scheduler. These bits of code relate to non-UI parts of the component, such as stores, models, utility classes etc. The second reason for …
Improving the Siesta automation
As you may already know, we use Siesta to test our own JavaScript components (Ext Scheduler and Ext Gantt) as well as Siesta itself. The test suites for our Ext JS components now consist of about 100 files for each product, meaning a couple of thousand assertions in total. More over we want our components to be compatible with at least the few most recent versions …