Unable to export test (version 3.17.2) #1839

TJSWANS300 · 2024-06-13T14:48:46Z

Hi.

For Selenium IDE (version 3.17.2), I have a test called Misc/Cleanup.

It is made up of 3 steps:

2 steps have the command run (which call another test)
the remaining step has the command close

When trying to export the Test to C# NUnit, the following error shows:

Could this be down to the Run command inside a test?

toddtarsi · 2024-06-13T15:45:20Z

Thats a good question. V3 is kinda hitting EOL. I have a recommendation that may help, or may hinder. In v4, I've cut the code export utilities into a standalone CLI tool using npm. Do you have npm on your computer? Basically, you can run code export as it's own utility this way if you do:

npm i -g side-code-export @seleniumhq/code-export-csharp-nunit
side-code-export @seleniumhq/code-export-csharp-nunit ./project.side ./tests

The advantage to doing this is that the stack trace is viewable and generally there is a lot less technology in the way.
Of course the issue is that some commands like storeXPathCount got the axe going from v3 to v4, but there is a migration utility too:

npm i -g side-migrate side-code-export @seleniumhq/code-export-csharp-nunit;
side-migrate ./project.side ./project-v4.side
side-code-export @seleniumhq/code-export-csharp-nunit ./project-v4.side ./tests-v4

TJSWANS300 · 2024-06-14T07:05:37Z

Thanks, I'll look into that

TJSWANS300 · 2024-06-14T07:44:19Z

I still have the same error doing that but we do have more detail:

CMD PROMPT
side-code-export @seleniumhq/code-export-csharp-nunit {Whole path to .side file} ./tests

CMD PROMPT OUTPUT
C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:46
function findReusedTestMethods(test, tests) {
^

RangeError: Maximum call stack size exceeded
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:46:31)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)

Node.js v20.12.2

TJSWANS300 · 2024-06-26T16:27:13Z

Any update on this?

toddtarsi · 2024-06-26T16:29:23Z

Ah shoot, no sorry. I first have to figure out a har file thing. However, fixing this should be a lot easier. The stack trace is right there. Can you give me a minimal side file that makes this issue? That will help me fix it faster. I'm sorry, you've caught me in the middle of basically a vacation from OSS.

TJSWANS300 · 2024-06-27T07:43:24Z

Here is a test side file that uses accounts.google.com with just 1 test

TestProject.zip

toddtarsi · 2024-06-29T09:31:35Z

Oh neat, basic recursion. Okay, I'll look into it! New core test unlocked

toddtarsi · 2024-06-29T23:46:04Z

@TJSWANS300 - New version going out now, I think it is quite good at recursion but please let me know what you think.

TJSWANS300 · 2024-07-01T09:44:56Z

@toddtarsi
I've had a look and still having the same error as before :(

Tried using the TestProject file above:

CMD PROMPT
side-code-export @seleniumhq/code-export-csharp-nunit Whole\path\to.side\file ./tests

CMD OUTPUT
C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:46
function findReusedTestMethods(test, tests) {
^

RangeError: Maximum call stack size exceeded
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:46:31)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)

Node.js v20.12.2

Does something need updating on my end?

toddtarsi · 2024-07-01T11:43:34Z

@TJSWANS300 - what do you get for this?

side-code-export --version

TJSWANS300 · 2024-07-01T12:41:33Z

@toddtarsi
4.0.11

toddtarsi · 2024-07-01T15:10:56Z

Huh! I'm stumped. I will try with the public binary in tonight. Sorry dude. I mean, there's even a command in the local codebase test:code-export that literally just tests export of script based recursion and dynamic script names.

TJSWANS300 · 2024-07-01T15:19:28Z

No worries at all.
Thought best to let you know.

TJSWANS300 · 2024-07-05T09:03:57Z

Any update on this?

toddtarsi · 2024-07-05T13:23:43Z

Ah, not yet. I'll take a look this weekend

TJSWANS300 · 2024-07-05T13:25:02Z

@toddtarsi
No worries - thank you

toddtarsi · 2024-07-12T16:27:51Z

I'm taking a look at this this weekend, I'm starting to use a 'top priority' label to prioritize what comes first, and this is on that list.

toddtarsi · 2024-07-16T03:15:43Z

@TJSWANS300 - Okay, just to be safe, I incremented again and tested locally using the recursion side file here:

https://github.com/SeleniumHQ/selenium-ide/blob/trunk/tests/examples/simple-parent.side#L85

(base) ➜  selenium-ide git:(trunk) ✗ npm ls -g side-code-export
├─┬ @seleniumhq/code-export-python-pytest@4.0.12
│ └── side-code-export@4.0.12
├─┬ selenium-ide@4.0.1-beta.14
│ ├─┬ @seleniumhq/code-export-csharp-nunit@4.0.12
│ │ ├─┬ @seleniumhq/code-export-csharp-commons@4.0.12
│ │ │ └── side-code-export@4.0.12 deduped
│ │ └── side-code-export@4.0.12 deduped
│ ├─┬ @seleniumhq/code-export-csharp-xunit@4.0.12
│ │ └── side-code-export@4.0.12 deduped
│ ├─┬ @seleniumhq/code-export-java-junit@4.0.12
│ │ └── side-code-export@4.0.12 deduped
│ ├─┬ @seleniumhq/code-export-javascript-mocha@4.0.12
│ │ └── side-code-export@4.0.12 deduped
│ ├─┬ @seleniumhq/code-export-python-pytest@4.0.12
│ │ └── side-code-export@4.0.12 deduped
│ ├─┬ @seleniumhq/code-export-ruby-rspec@4.0.12
│ │ └── side-code-export@4.0.12 deduped
│ └── side-code-export@4.0.12
└── side-code-export@4.0.12

(base) ➜  selenium-ide git:(trunk) ✗ side-code-export ./packages/code-export-python-pytest/dist/index.js ./tests/examples/simple-parent.side ./output-tests
Encountered a dynamic test declaration, including all tests as methods - will bloat code
Encountered a dynamic test declaration, including all tests as methods - will bloat code
Encountered a dynamic test declaration, including all tests as methods - will bloat code
Encountered a dynamic test declaration, including all tests as methods - will bloat code
Encountered a dynamic test declaration, including all tests as methods - will bloat code
Encountered a dynamic test declaration, including all tests as methods - will bloat code
Encountered a dynamic test declaration, including all tests as methods - will bloat code
Encountered a dynamic test declaration, including all tests as methods - will bloat code
(base) ➜  selenium-ide git:(trunk) ✗

Seems to transpile fine on latest!

TJSWANS300 · 2024-07-16T07:16:01Z

@toddtarsi
I've had a look and still having the same error as before :(

Tried using the TestProject file above:

CMD PROMPT
side-code-export @seleniumhq/code-export-csharp-nunit Whole\path\to.side\file ./tests

CMD OUTPUT
C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:46
function findReusedTestMethods(test, tests) {
^

RangeError: Maximum call stack size exceeded
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:46:31)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)
at findReusedTestMethods (C:\Users\{username}\node_modules\side-code-export\dist\code-export\find.js:53:42)

Node.js v20.12.2

side-code-export --version = 4.0.12

Does something need updating on my end?

toddtarsi · 2024-07-16T14:27:14Z

Damn, @TJSWANS300 - Can you post a side file reproduction? I'm a bit confused because yeah this is now part of the core CI:

https://github.com/SeleniumHQ/selenium-ide/blob/trunk/package.json#L25

Basically, this has a recursive test that does some dynamic stuff, and I don't think yours does. I need to figure out that difference so I can make it a core test too.

TJSWANS300 · 2024-07-16T14:40:38Z

Damn, @TJSWANS300 - Can you post a side file reproduction? I'm a bit confused because yeah this is now part of the core CI:

https://github.com/SeleniumHQ/selenium-ide/blob/trunk/package.json#L25

Basically, this has a recursive test that does some dynamic stuff, and I don't think yours does. I need to figure out that difference so I can make it a core test too.

Here is a test side file that uses accounts.google.com with just 1 test

TestProjectIDE.zip

toddtarsi · 2024-07-16T15:27:46Z

@TJSWANS300 - Thank you, if I'm caught up on work tonight, I'll take a look. I want recursion to be fully functional in code-export, and will make sure of it.

TJSWANS300 · 2024-07-22T18:25:37Z

Any update on this?

toddtarsi · 2024-07-22T18:39:44Z

Nah, sorry. It's one of like four issues with top priority (key-chord support in sendKeys, nested variable paths in sendKeys, multi layer recursion, break-fixing javascript-mocha code-export). It's getting worked on, but I'm kinda shelved for a week or two unfortunately.

TJSWANS300 · 2024-07-22T18:41:24Z

No worries

toddtarsi · 2024-07-22T18:42:44Z

Thank you

toddtarsi mentioned this issue Jun 28, 2024

export python assert ${val} become a string #1244

Open

toddtarsi added the top priority Issues where the user helped on the codebase or this blocks the main user groups. label Jul 12, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to export test (version 3.17.2) #1839

Unable to export test (version 3.17.2) #1839

TJSWANS300 commented Jun 13, 2024

toddtarsi commented Jun 13, 2024 •

edited

Loading

TJSWANS300 commented Jun 14, 2024

TJSWANS300 commented Jun 14, 2024 •

edited

Loading

TJSWANS300 commented Jun 26, 2024

toddtarsi commented Jun 26, 2024 •

edited

Loading

TJSWANS300 commented Jun 27, 2024

toddtarsi commented Jun 29, 2024

toddtarsi commented Jun 29, 2024

TJSWANS300 commented Jul 1, 2024 •

edited

Loading

toddtarsi commented Jul 1, 2024

TJSWANS300 commented Jul 1, 2024

toddtarsi commented Jul 1, 2024 •

edited

Loading

TJSWANS300 commented Jul 1, 2024

TJSWANS300 commented Jul 5, 2024

toddtarsi commented Jul 5, 2024

TJSWANS300 commented Jul 5, 2024

toddtarsi commented Jul 12, 2024

toddtarsi commented Jul 16, 2024

TJSWANS300 commented Jul 16, 2024

toddtarsi commented Jul 16, 2024

TJSWANS300 commented Jul 16, 2024

toddtarsi commented Jul 16, 2024

TJSWANS300 commented Jul 22, 2024

toddtarsi commented Jul 22, 2024 •

edited

Loading

TJSWANS300 commented Jul 22, 2024

toddtarsi commented Jul 22, 2024

Unable to export test (version 3.17.2) #1839

Unable to export test (version 3.17.2) #1839

Comments

TJSWANS300 commented Jun 13, 2024

toddtarsi commented Jun 13, 2024 • edited Loading

TJSWANS300 commented Jun 14, 2024

TJSWANS300 commented Jun 14, 2024 • edited Loading

TJSWANS300 commented Jun 26, 2024

toddtarsi commented Jun 26, 2024 • edited Loading

TJSWANS300 commented Jun 27, 2024

toddtarsi commented Jun 29, 2024

toddtarsi commented Jun 29, 2024

TJSWANS300 commented Jul 1, 2024 • edited Loading

toddtarsi commented Jul 1, 2024

TJSWANS300 commented Jul 1, 2024

toddtarsi commented Jul 1, 2024 • edited Loading

TJSWANS300 commented Jul 1, 2024

TJSWANS300 commented Jul 5, 2024

toddtarsi commented Jul 5, 2024

TJSWANS300 commented Jul 5, 2024

toddtarsi commented Jul 12, 2024

toddtarsi commented Jul 16, 2024

TJSWANS300 commented Jul 16, 2024

toddtarsi commented Jul 16, 2024

TJSWANS300 commented Jul 16, 2024

toddtarsi commented Jul 16, 2024

TJSWANS300 commented Jul 22, 2024

toddtarsi commented Jul 22, 2024 • edited Loading

TJSWANS300 commented Jul 22, 2024

toddtarsi commented Jul 22, 2024

toddtarsi commented Jun 13, 2024 •

edited

Loading

TJSWANS300 commented Jun 14, 2024 •

edited

Loading

toddtarsi commented Jun 26, 2024 •

edited

Loading

TJSWANS300 commented Jul 1, 2024 •

edited

Loading

toddtarsi commented Jul 1, 2024 •

edited

Loading

toddtarsi commented Jul 22, 2024 •

edited

Loading