Skip to content

Releases: testxio/testx

2.11.2

Choose a tag to compare

@greyarch greyarch released this 28 Jul 13:56
  • Improved promise handling when executing keywords

2.11.1

Choose a tag to compare

@greyarch greyarch released this 10 Jul 08:54
  • Fixed switch to keyword - PR-16. Thanks to Vince.

2.11.0

Choose a tag to compare

@greyarch greyarch released this 25 May 12:12

Allow prefixing of object names when adding them.

Let's say in your objects file (my-objects.js) you have an object defined like this

...
coolObj: css("input.thing")
...

In your config file, you'd do

testx.objects.add(require("my-objects"), "somePrefix.")

and in the tests, you can use it like this

- set:
    somePrefix.coolObj: "some text"

2.10.0

Choose a tag to compare

@greyarch greyarch released this 08 May 15:15
  • Check matches keyword is extended to support checking of attributes. Here is how you'd do it:
- check matches:
    myPrettyObject:
      title: Something funny
      href: https

This will check that the title attribute of myPrettyObject object regex matches "Something funny" and the href attribute matches "https".

2.9.2

Choose a tag to compare

@greyarch greyarch released this 30 Mar 09:19
  • FIX: The default behaviour for a textarea should get its value.

2.9.1

Choose a tag to compare

@greyarch greyarch released this 22 Mar 15:17
  • FIX: was handling incorrectly valueless set parameters.

2.9.0

Choose a tag to compare

@greyarch greyarch released this 20 Mar 10:45

Added special behaviour for setting check boxes and radio buttons. You can now specify the resulting state of this type of elements or just click them regarding of their current state.

If you specify true as the value to set the checkbox (or radio button) to, testx will make certain that this element is checked . This means that If it is already checked nothing will happen and if it is not, it will be clicked (checked). If you specify false as the resulting state the element will be clicked if it is checked, or if it is unchecked nothing will happen.

If you omit the value (set it to null) the element will be clicked regardless.

Something like this. The example is valid for both check boxes and radio buttons:

- set:
    # nothing happens - the elements are already in the state you require
    checkboxChecked: true
    checkboxUnchecked: false

- set:
    # the elements get clicked, their state is set to unchecked and checked respectively
    checkboxChecked: false
    checkboxUnchecked: true

- set:
    # both elements get clicked, regardless of their initial state
    checkboxChecked:
    checkboxUnchecked:

2.8.0

Choose a tag to compare

@greyarch greyarch released this 13 Oct 13:44
  • Support for ${exp} expression resolution. It is the same as the current {{exp}} format. For backwards compatibility {{exp}} is supported as well, but may be dropped in testx@3.0.

2.7.1

Choose a tag to compare

@greyarch greyarch released this 13 Oct 05:23
  • Added more tests for comparing complex structured data
  • Removed redundant code

2.7.0

Choose a tag to compare

@greyarch greyarch released this 12 Oct 20:32
  • Allow for invocation of functions with arguments from context. For example, if the test context contains a function test that accepts 1 argument, this is now possible:
- some keyword:
     first arg: '{{test("some value")}}'

The function argument doesn't need to be a literal, it can also be a variable from the test context. Essentially the function invocation is evaluated in the current test context.
It is possible to pass arbitrary number of arguments.