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
Functionality is working but tests failing for delete from dashboard and from garden show page.
Couldn’t figure out how to hit the destroy action in pry and felt that I was spending too much time on it given the functionality is working.
Also the entire test is stubbed and isn’t actually testing anything anyway (as a lot are on the FE). Would like to address these concerns w/ Ian or the group.
Response from Ian regarding above:
Ian Douglas 1:08 PM
in a nutshell, it's tricky to actually test the front end unless you deploy a second copy of the backend and treat that as a "test" or "staging" environment, and set that ENV hostname on Travis for the FE code to hit "for real" and switch to using VCR
without getting into paid Travis "pipeline" environments where it spins up all other services in order to properly run all test suites, there's no easier way than just deploying a second copy of BE
The text was updated successfully, but these errors were encountered:
Functionality is working but tests failing for delete from dashboard and from garden show page.
Couldn’t figure out how to hit the destroy action in pry and felt that I was spending too much time on it given the functionality is working.
Also the entire test is stubbed and isn’t actually testing anything anyway (as a lot are on the FE). Would like to address these concerns w/ Ian or the group.
Response from Ian regarding above:
Ian Douglas 1:08 PM
in a nutshell, it's tricky to actually test the front end unless you deploy a second copy of the backend and treat that as a "test" or "staging" environment, and set that ENV hostname on Travis for the FE code to hit "for real" and switch to using VCR
without getting into paid Travis "pipeline" environments where it spins up all other services in order to properly run all test suites, there's no easier way than just deploying a second copy of BE
The text was updated successfully, but these errors were encountered: