Skip to content
This repository has been archived by the owner on Jul 22, 2020. It is now read-only.

Introduce end-to-end testing [5] #17

Open
planger opened this issue Dec 20, 2018 · 2 comments · May be fixed by #141
Open

Introduce end-to-end testing [5] #17

planger opened this issue Dec 20, 2018 · 2 comments · May be fixed by #141
Assignees
Labels

Comments

@planger
Copy link
Contributor

planger commented Dec 20, 2018

Investigate and select the best fit for a e2e testing technology, such as puppeteer, silenium, testcafe, and start creating a couple of smoke-tests.

@JonasHelming JonasHelming added this to the lab milestone Nov 15, 2019
@JonasHelming JonasHelming changed the title Introduce end-to-end testing Introduce end-to-end testing [3] Nov 15, 2019
@JonasHelming JonasHelming changed the title Introduce end-to-end testing [3] Introduce end-to-end testing [5] Nov 29, 2019
@JonasHelming JonasHelming modified the milestones: lab, M1: Ecore Diagrams Mar 24, 2020
@sgraband
Copy link
Collaborator

sgraband commented Apr 8, 2020

@JonasHelming @CamilleLetavernier I got the tests running in travis, however they all seem to fail, because the Classes cannot be found, since i am relying on the generated Class names. One solution would be to rename the classes every time, but this will take additional time.

Another solution would be to create a test.ecore, that i will use for the test-cases. This would probably fix the problem with Travis and could potentially lower the runtime in general.

Should i do it that way? If yes, the Ecore should probably be in another workbench than the example one, right?

@CamilleLetavernier
Copy link
Contributor

Using a different workspace (and set of models) for tests makes sense, yes

@sgraband sgraband linked a pull request Apr 14, 2020 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants