Support Forum

I have first test that creates User_TIMESTAMP.
I want second test to do some stuff with this user and the 3rd test to delete them.
What is good way to pass that user name User_TIMESTAMP between the two tests?

Without the test case, consider the following routine: 1) I click button 2) Ajax request happens 3) Another AJAX sequenced afterwards 4) A data view is then refreshed with a mask over it 5) As a part of that 2nd AJAX coming back, we also set some values on the form 6) 10 ms dirtycheck (part of ExtJS...

Strange because it works with it in all the other cases. It's kind of confusing because Sencha has ComponentQuery and siesta has CompositeQuery, and you never know which one you're using. At the end of the day this doesn't really answer how I can debug Siesta effectively in a case of this error. Sti...

I did want to point out a strange observation in regards to waitForComponentQueryVisible method. The debugger claims it comes from Siesta.Test. SenchaTouch [waitForComponentQueryVisible] This is strange because it's an ExtJS app. If I scroll a bit up in debugger, I run into: Role('Siesta.Test.ExtJS....

I thought I was a pretty expert with using debugger (debug ExtJS all day long), but boy trying to debug Siesta was a miserable experience. While I'm able to break on the fail() method to catch the time when my error is about to be printed by Siesta, I get no indication in the stack trace as to where...

I've put together a pretty lengthy test (500+ lines) and the very last actions in this test are failing with some pretty generic errors: waitForComponentQueryVisible checker threw an exception Failed assertion `waitForComponentQueryVisible` Exception: "TypeError: Cannot read property 'items' of...

Hey that seems to be working!

Is there a list of these special methods like "contains"?

Just to be specific on that error message: WARN: getNormalizedTopElementInfo: Target element of action [simulateMouseClick] is not visible or not reachable: #ext-gen1173 It's so annoying. The reason we're entertaining replacing our current QA infrastructure is because it takes forever to run anythin...

One of the main reasons for evaluating Siesta was the fact that it's closely integrated with some of the ExtJS features. This was evident when I discovered methods like waitForViewRendered, specifically targeted at ExtJS dataviews. To my disappointment, that didn't help me very much. Consider the fo...

Actually there were issues. The runInPopup configure is the only working version for me at this point it seems. Read more here: https://forum.bryntum.com/viewtopic.php?f=20&t=6065

Still, thanks!