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

Add integration test #11

Open
3 tasks
vortizhe opened this issue Jun 21, 2018 · 1 comment
Open
3 tasks

Add integration test #11

vortizhe opened this issue Jun 21, 2018 · 1 comment
Assignees
Milestone

Comments

@vortizhe
Copy link
Member

We must add integration test before publishing the first version.

  • Create a phoenix app only in dev and test
  • Add hound for integration text with chrome driver
  • Test connection and basic actions
    • redirect
    • replace_with
    • append
    • prepend
    • mod_class
@vortizhe vortizhe added this to the v1.0.0 milestone Jun 21, 2018
@vortizhe vortizhe self-assigned this Jun 21, 2018
@crbelaus
Copy link
Contributor

Since we have to build a Phoenix application to run the integration tests, it may be a good idea to reuse that application as an easy platform where we can implement and try new features.

It could be also very useful to put that application running somewhere public-accessible, so potential users could see Frankt working before trying it in their projects.

As explained in the Phoenix docs, Heroku has some limitations regarding long-lived connections and processes. The most easy alternative seems to be Gigalixir.

@crbelaus crbelaus mentioned this issue Jun 28, 2018
19 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants