Search:

Fabulous, that's it!

Excellent, thanks!
While your answer probably works most of the time, for me it was necessary to add .rowAt(0, 60000).grid() before the execute(..). function because in my case the grid's entries...

This works but has an interesting quirk. If the browser that is automatically launched during the test run is not manually maximized to completely fill the screen,
ST is not able to select the item...

Say I have a grid and want to extract its records.



let record = {};
grid.rowAt(rowIndex)
.cellAt(cellIndex)
.focus()
.get('innerText')
.and(function (future) {

Is there a way to clear an input field while using the ST.component("locator"); API?
Using ST.component("locator").setValue(""); results in the following error:



TypeError:...

Hmm no, sadly this does not work. I've send you a private message with an example so you can see it yourself

The 'General' node expands itself after typing so that shouldn't be a problem.

Also I should probably mention that I somehow need to work with the reportId, which is our internal way of...

Sadly your suggestion throws the following error: Timeout waiting for target to be visible for ST.future.Row. Fix the error and try recording again.

Here are the attachments, hope it works this...

I tried adapting what I've seen in this thread https://www.sencha.com/forum/showthread.php?472443-Clicking-an-item-from-the-combobox-drowpdown and apply it to my use case, but I keep getting errors....

Say I am writing a bit of non-ST code inside a seperate function and may want to make my test fail or continue based on this functions result.

How would I do this?

I've seen some stuff in the...

Is it possible to catch errors thrown by ST and handle them as I wish to?

For example catching the error that occurs when a row can not be located due to an invalid rowindex?




try {
...

Okay after trying out your suggestions this seemed to work out:



it("check the grid for the updated record", function (done) {
ST.wait(4000)
.and(function () {
...

So I have this piece of code that tests whether a grid gets updated after having made a change to one of its records or not.

The alert()-method clearly prints out the correct rowIndex and I've...

Hey, is this also possible when using page objects? e.g.: stpo.custompage.myElement(10000); ?

Hmm yes, that would work.

Although,


.execute(function(grid) {
would now be


.execute(function(row) {

Ah, I found the problem!

Turns out it wasn't the locators as I previously suspected.

The grid's records get fetched from a DB and as I invoke the execute function right after navigating to the...

Thanks,

the KitchenSink version works perfectly fine, but transferred to my site I am running into a problem.

Executing the findby-Method directly in the Browser gives me the desired rowIndex:...

Say I have a grid where a row is uniquely identified by a combination of two or more columns (in my case 3); a composite key.

In this scenario there are 2^3 possible combinations


...

Thank you so much!

A small addition to your solution:
module.id gets the file location using '\' instead of '/' so the subtstring method has to be altered the following:



describe('File...

I have written a short test that fetches login credentials from a local file using the fs-module and logs in.



describe("loginAndNavigate", function() {
const fs = require('fs');

//...

I have written a short test that fetches login credentials from a local file, logs in and simply accesses a page element.



describe("loginAndNavigate", function() {
const fs =...

Hello,
I was wondering if it is possible to run test cases with command-line arguments respective to JAVA applications and their String[ ] args parameter...

That's a great idea, I'll definitely try using direct DB queries.

But it would still be more elegant to remove these entries after a test has run, right?

Is there sth. comparable to a...

In order to test some functionalities of a grid we have on our website I am currently creating new entries for each test run that I can then alter and act on in my test suites.

After the tests...

I'll answer that myself:

the .expect('innerText').toBe('string'); behaves the same as the text()-Method, even checks for the actual (not only displayed) value.
Its toBe() can be preponed with...