ajarproject / aj_tools_unittest Goto Github PK

Describe the bug
In the Unit Test Main Window window, the "open method" button doesn't work

To Reproduce

1. Install the Unit Test Component
2. run AJ_Tools_UT_LaunchMainWindow
3. Run tests
4. press the "Open Method" Button

Current behaviour

Desktop (please complete the following information):

• Windows 10
• 4D V18R4
• 2.2.0+Build37

Is your feature request related to a problem? Please describe.

I understand that the delay in AJ_Tools_UT_assert is to show that the unit tests are running, but when there are thousands of tests, those extra wait can turn into minutes. If there are thousands of tests, the interface will show progress because it takes time to run many tests.

Describe the solution you'd like

From the method AJ_Tools_UT_assert delete the line:

DELAY PROCESS:C323(Current process:C322; 2)

Describe alternatives you've considered

An alternative would be only use delay only when there is less then 100 asserts.

Is your feature request related to a problem? Please describe.
Some people might not realize that you can open or close a section.

Describe the solution you'd like
Add a "style="cursor: pointer" so that the clickable elements to have a pointer cursor

We have been using the Unit Testing Component for over a month now and we find it very useful. However, we have some old unit-tests that were written using the ASSERT command. We found out that it's so much easier to have an equivalent AJ_Assert to replace one ASSERT with 1 AJ_ASSERT. So that we can quickly convert our old methods.

ASSERT($success=True;"Expected true for success") // Old way
AJ_ASSERT($test;$success;True;$given;"Expected true for success") // New Way

We find it much easier to convert our old unit-tests to the new AJAR compliant one using this helper method.
The code for AJ_ASSERT is something simple like this:

$test:=$1
$test.expected:=$2
$test.actual:=$3
$test.given:=$4
$test.should:=$5
$test.assert()

Describe the bug
When i execute a test i have an error on the method Rappel Externe.
With the trace i see it's located on the method Type Valeur, but i don't know why.

To Reproduce
Steps to reproduce the behavior:

1. Create a test
2. Execute the test
3. At the end of the test the error came

Current behavior
I have 3 error box per test.

Expected behavior
No error should appear.

Screenshots

Desktop (please complete the following information):

• OS: MacOs BigSur
• 4D V18R5

Do you plan to release the Component compiled for Apple Silicon (Universal binary) also?

The Issue

Let's say we have written 1000 unit tests for our application and it's time to write test #1001. So when we write a new test method, we want a quick way to run the test the method #1001 without having to go through the previous 1000. The problem is that it takes a long time (in our case 10mins and growing) to run all the previous tests and rebuild the hierarchical list.

Suggested Solution

A button on the Unit Test Panel to update the hierarchical listbox without running the tests. This button will refresh the list with all the new methods that have been created. Then we can selectively run the new tests without having to wait.

Our current solution to this problem

We write every test method twice. One time using 4D's ASSERT command; we run and execute it. Once the test passes, then we rewrite the method using the AJ ASSERT method. This is quite time-consuming.

• This is one of the most wanted feature in our group of developers.

Is your feature request related to a problem? Please describe.
When I have a lot of method I have to struggle to open the failing method

Describe the solution you'd like
I would like to have a button in the web view to be able to open directly the test method

If there are thousands of tests, each with dozens of assert tests, how do I figure out what assert in which test method throws this error?

Please add the method name and a assert number with in the ASSERT message.

Is your feature request related to a problem? Please describe.
The way the parsing works is that it need to execute all the method in order to only know the list of tests. That mean it need to execute all the tests only to get a list.

Describe the solution you'd like
Rewrite the way the component work in order to not have to execute all the tests

Describe alternatives you've considered
js.component is a very good alternative to write unit test (I actually use it instead of my own component) but is not free.

Additional context
It would help to solve some existing issue and some feature request that has been there for too long now. (sorry)

Is your feature request related to a problem? Please describe.
If the assert missing data, it doesn't display in the result window and cannot inform me where the issue is located.

Describe the solution you'd like
Insert the assert test as a failed, maybe with a different colour background to indicated the unit test method fails the test.
But instead of showing expected/actual in the detail, show the assert message.

Is your feature request related to a problem? Please describe.
It is hard for me search the failed test in large amount of passed tests. I don't want to see passed tests if I am searching for failed tests.

Describe the solution you'd like
A way to filter out the passed tests and show only the failed tests.

Describe alternatives you've considered
Pressing the fail count will closes all the passed tests.
In list box allowing sorting of passed and failed tests