-
The existing unit tests (Firmware/unittests) are written without any test framework and lack proper return value checking (they are in fact test harnesses). Moving them to G test would be a great firs…
-
```
What steps will reproduce the problem?
"solo.clickOnButton("Yes");" assert-fails with "Button with the text: Yes is
not found!", while the text Yes on a button in a dialog is clearly on screen.
…
-
```
What steps will reproduce the problem?
"solo.clickOnButton("Yes");" assert-fails with "Button with the text: Yes is
not found!", while the text Yes on a button in a dialog is clearly on screen.
…
-
```
What steps will reproduce the problem?
"solo.clickOnButton("Yes");" assert-fails with "Button with the text: Yes is
not found!", while the text Yes on a button in a dialog is clearly on screen.
…
-
```
What steps will reproduce the problem?
"solo.clickOnButton("Yes");" assert-fails with "Button with the text: Yes is
not found!", while the text Yes on a button in a dialog is clearly on screen.
…
-
I've been hitting Concurrent::RejectedExecutionError when running my test-stuite. It was ok with MRI, but switching to JRuby was the game-changer. It turns out there seems to be an at_exit trap that s…
-
```
What steps will reproduce the problem?
"solo.clickOnButton("Yes");" assert-fails with "Button with the text: Yes is
not found!", while the text Yes on a button in a dialog is clearly on screen.
…
-
```
What steps will reproduce the problem?
"solo.clickOnButton("Yes");" assert-fails with "Button with the text: Yes is
not found!", while the text Yes on a button in a dialog is clearly on screen.
…
-
```
What steps will reproduce the problem?
"solo.clickOnButton("Yes");" assert-fails with "Button with the text: Yes is
not found!", while the text Yes on a button in a dialog is clearly on screen.
…
-
```
What steps will reproduce the problem?
"solo.clickOnButton("Yes");" assert-fails with "Button with the text: Yes is
not found!", while the text Yes on a button in a dialog is clearly on screen.
…