Forum Discussion

StankoMilosev's avatar
StankoMilosev
New Contributor
3 hours ago
Solved

Export to HTML with a long path name

Hello, I have test with many child tests like this:   test/ ├── childtest/          ├── childtest1/                   ├── childtest1a/                            ├── childtest1a-i/           ...
  • rraghvani's avatar
    rraghvani
    2 hours ago

    I've never come across this issue before, nor have I seen anyone else mention it on the forum.

    Your folder structure, while valid, is outdated and overkill for human use. It's too deeply nested and overly verbose, which creates several issues:

    • Hard to navigate: Drilling down 8+ levels just to reach something is inefficient.
    • Fragile paths: Long paths are tedious to type, easy to break, and can hit system limits.
    • Low readability: Names like childtest1a-i-1-a-x-final don't convey meaning - they just encode hierarchy.
    • Maintenance pain: Refactoring or moving things later becomes cumbersome.

     

    Aim for a better folder structure with:

    • A shallow hierarchy (ideally 3 - 5 levels max)
    • Meaningful names (based on purpose, not position)
    • Logical grouping (by feature, type, or domain)
StankoMilosev's avatar
StankoMilosev
New Contributor
2 hours ago

The names I used here are just examples; they are not from a real case. From my point of view, the structure follows small logical steps, and it is easier to move and maintain compared to grouping everything into one large test.

 

I am still learning the best way to write tests, and now I see that this approach may not work well in TestComplete. I just wanted to be sure.

 

Thank you for your help.

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    2 hours ago

    Don't overcomplicate things early on, especially while you're still learning. Start simple, then improve based on feedback and experience - this a very practical and widely accepted approach.

    My result folder structure looks like this,

    Folders are created based on timestamp, of when the projects were executed.Folder contents include the resultsResults

    Once the automation completes, I get a summary email and a link to the folder containing the results.

    This was created after I had my automation fully working.