I'm still for the migration to Cypress, Tibor. Thanks for the PR and for
circling back on this thread.
On Tue, Oct 30, 2018 at 6:39 AM Tibor Meller wrote:
> Hi All,
>
> To continue this thread and keep you updated I would like to share that I'm
> opened a PR with Cypress UI tests for PCAP.
> I w
Hi All,
To continue this thread and keep you updated I would like to share that I'm
opened a PR with Cypress UI tests for PCAP.
I was also able to integrate these tests into Travis CI.
https://github.com/apache/metron/pull/1226
You can find more information in the PR description.
I also opened a
Great Guys! Thanks for the feedback. I'll move forward as discussed.
Thx
On Wed, Sep 26, 2018 at 11:44 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> I'm good with it. We can see some tests in action (and hopefully running in
> Travis! :-D) and then migrate and deprecate Protractor
I'm good with it. We can see some tests in action (and hopefully running in
Travis! :-D) and then migrate and deprecate Protractor accordingly if we
still agree that's the way to go. When you submit the first PR, please link
to this DISCUSS via permalink from the mailing list archives. Thanks guys.
I think Tibor's idea of using PCAP tests as an introduction to Cypress for
Metron is a great idea. As he pointed out, PCAP tests can take advantage of
Cypress' capability to mock responses, and we can set it up to run in
Travis. Once the community is able to see the benefits from an actual set
of C
Hi Team,
Many of us agreed on that Cypress could be a more capable tool for us to
write high-level UI tests, whether those be e2e, integration or automated
regression tests. If there is no open question left about cypress we could
to bring it a test drive. My suggestion is to implement the PCAP UI
That's good feedback, thanks Shane!
On Thu, Sep 20, 2018 at 6:23 AM Shane Ardell
wrote:
> While the Cypress team suggests taking advantage of stubs where you can,
> especially during development, we would definitely be able to test real
> endpoints [1]. It can be used exactly like how Protractor
While the Cypress team suggests taking advantage of stubs where you can,
especially during development, we would definitely be able to test real
endpoints [1]. It can be used exactly like how Protractor is used, but with
the many benefits and features it provides [2]. Cypress also offers tools
for
Shane,
Can you elaborate on the testing model you're proposing? I looked through
the overview and some of the documentation. As far as I can tell, this
would effectively be and e2e test for the UI *only*, so we would be missing
testing the actual integration points with the REST API or any other
p
This article comparing the two is not favorable for Cypress. Are any of these
concerns relevant to us? If not, then I think Cypress is fine
https://hackernoon.com/cypress-io-vs-protractor-e2e-testing-battle-d124ece91dc7
Hello everyone,
Currently, we use Protractor to run our UI "end-to-end" tests. However,
there are a handful of major advantages we can gain from switching to
Cypress: https://www.cypress.io/features/.
- As with most Selenium-based e2e testing frameworks, Protractor suffers
from test flakine
11 matches
Mail list logo
