You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
As described in https://github.com/oasp/oasp4js/wiki/Testing, we should have client-side tests against the browser, while the server is replaced by a client-side test double. According to the AngularJS tutorial, for this kind of test we should use Protractor. Unfortunately, I could not find an example using Protractor in the restaurant application.
I would like to clear up the following questions:
Do we want to use Protractor or is there a better tool for this kind of test?
Is it possible to replace the server by a test double when using Protractor (e.g. with $httpBackend.whenGET/POST/etc.)?
Furthermore, it would be fine to add an example test to the restaurant application, which should be part of this issue's definition of done.
The text was updated successfully, but these errors were encountered:
As described in https://github.com/oasp/oasp4js/wiki/Testing, we should have client-side tests against the browser, while the server is replaced by a client-side test double. According to the AngularJS tutorial, for this kind of test we should use Protractor. Unfortunately, I could not find an example using Protractor in the restaurant application.
I would like to clear up the following questions:
Furthermore, it would be fine to add an example test to the restaurant application, which should be part of this issue's definition of done.
The text was updated successfully, but these errors were encountered: