Actually I have similar questions. I would like to separate test data, HTTP mocks(Restangular) and Angular UI tests into separate suites.
The Jasmine code that I have inherited looks scary now. Can I test HTML 5 UI to check if Angular model is accessible ?
What is a good resource for Angular mocks dealing with a e2e setup like this ?
After a lot of problems I am using rspec/capybara (and database cleaner) for the Angular e2e tests. So I can use FactoryGirl for my test data, authentication helpers, ... - and everything is working perfect without any troubles. I don't like testing only two different things (API and frontend only with mocked API) seperate - always missing some bugs in such scenarios. Can use this for load tests too. So why don't you use Capybara only because you are using a different frontend framework?
I don't like to use Rails because I think the frontend and the backend should be independent. My angular app have to consume a Rest API but I don't care where the data come from. Furthermore, I have to have an open-source application. I don't want to force the contributor to install Rails to develop a JS app.
You don't have to use anything from the frontend part ;)
Rails is great for constructing the REST API. At one of my projects I have the backend (Rails) even in it's own repository. So the frontend guys just check it out and run the tests. With rspec even non ruby developers where able to write the tests within minutes. But you can try to clean the database in a generic solution for any backend. If you find any useful sulution please tell me ;)
Rails is great for constructing the REST API. At one of my projects I have the backend (Rails) even in it's own repository. So the frontend guys just check it out and run the tests. With rspec even non ruby developers where able to write the tests within minutes. But you can try to clean the database in a generic solution for any backend. If you find any useful sulution please tell me ;)
댓글 없음:
댓글 쓰기