Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change hierarchy in Che repo to separate tests

See original GitHub issue

Is your task related to a problem? Please describe.

There are already some test folders in the che root - e.g. e2e, selenium. Other tests are about to be added here (e.g. load tests) so the root will be quite chaotic.

Describe the solution you’d like

We decided to separate tests related stuff to the tests folder. There is a POC hierarchy that should be created:

che
 - assembly
 - ...
 - tests
   - e2e
   - functional (previous selenium)
   - performance
   - jenkins

Describe alternatives you’ve considered

The proper name of folders is not final. All ideas on naming are welcome, it would be nice to have that named properly.

Additional context

As a part of this issue, there would be also changes in pom.xml and build scripts - don’t forget! 😃

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:8 (8 by maintainers)

Top GitHub Comments

2reactions

Katka92commented, Oct 31, 2019

I don’t like having technology as a main name of tests, but I’m afraid I can not come up with something better now. I would add at least the word test to the technology. So the final structure should be like this:

tests
    - e2e
        - typescript-tests
        - java-tests
    - performance
    - .infra

1reaction

dmytro-ndpcommented, Oct 31, 2019

Agree with the next project structure:

tests
    - e2e
    - legacy-e2e
    - performance
    - .infra

Top Results From Across the Web

Testing best practices - GitLab Docs

All new spec files are run in random order to surface flaky tests that are dependent on test order. When randomized: The string...

Separate or project repository to store tests? Which, why, and ...

Separating the repositories keeps more clean environment. Repositories contain only things it's concerned about.

Getting changes from a Git Repository - GeeksforGeeks

--rebase: When a git pull command is called it will merge two branches and will create a separate branch which inherits the changes...

Name Mapping | TestComplete Documentation

The Name Mapping repository stores object identification information separately from tests making test maintenance easier. If your application changes, ...

basic administration - Gitolite

Go to the server and rename the repo at the Unix command line. Don't forget to retain the ".git" extension on the directory...