Search found 12 matches

How soon in Q2? We'd like to be able to turn code coverage back on in our release pipeline as soon as possible.
I was just reviewing the documentation for Siesta when I noticed how old the screenshots are. As a developer, I know how time-consuming it can be to update things like that, but Siesta would likely be received better by people new to the testing suite and wanting to give it a try. Looks go a long wa...
@mats, I was looking at the Getting Started guide, which references how to add Ext 4.2 to your index file in order to get Siesta to run, which is definitely no longer the case. The screenshots look to be outdated as well.

https://www.bryntum.com/docs/siesta/#!/g ... ng_started
Where is the documentation for Siesta 3?

I don't see it on the site, nor is it in the zip file for Siesta 3.
I was able to get it up and running by using code from one of the examples files, but surely including old documentation with the new release was an accident?
Are there any defined times that a Bryntum employee is expected to be in the IRC chat? I've checked at various times, and I've only seen nickolay in there, and only one time, and even then he quickly left. Is the IRC room a terrible way to reach out to you guys? If so, that page may need to be updat...
I just wanted to remind you guys at Bryntum that you've undoubtedly been busy with SenchaCon and forgot (or haven't had time) to update your Siesta screenshots to match your updated product. The most obvious places being: * The Bryntum home page slider. * The Siesta project page. Let Siesta put its ...
I would like to have the ability to do a "dry run" that allowed you to quickly identify what tests are going to be run based on your --include and --exclude options.
I agree. This feature would be a useful one.
That is correct. The test is to ensure a warning message appears before the user is logged out from inactivity, so the majority of the test is simply waiting.
It's a fairly simple change, so please see the attached patch file to be applied to bin/phantomjs-launcher.js. Sorry it's not a patch file by default, but the forums wouldn't allow that file type as an attachment.