search

CyberCRI / learn-ext

WeLearn Browser Extension
https://welearn.cri-paris.org
MIT License
11 stars 1 forks source link

Integration tests #125

Open iryna1 opened 4 years ago

iryna1 commented 4 years ago

Check that input and outputs are ok in APIs

iryna1 commented 4 years ago

A suggestion of Prashant: do an "acceptance test" instead. To be decided among the developers.

prashnts commented 4 years ago

Suggested test runners:

prashnts commented 4 years ago

There is a unit test covering only a small portion of code, which is already set up as a CI using GitHub Actions.

https://github.com/CyberCRI/learn-ext/runs/497870784?check_suite_focus=true

nicolasz-cri commented 4 years ago

Suggested test runners:

Yes it useful too. But this is e2e front test. I try to implement integration test for endpoints. Both should be done at some point !

@iryna1 FYI: If you don't know what is the pyramid of test, you can read that :

prashnts commented 4 years ago

I did not know about this, thanks! I agree that integration test is probably faster to realise, since for e2e test (I called it "acceptance test", not sure why...) we will need to spin up a server, and database instance, with a separate keycloak client ids. Essentially we'll need to instrument the whole stack before we can do the e2e tests.