Backend Adapters

[RandallKent]

While Cypress does provide documentation on testing your app, there are times when you need to interact with the backend at a deeper level.

Language	Repo	Status
Ruby	cypress-adapter-ruby
Node	cypress-adapter-node
Python	cypress-adapter-python
PHP	cypress-adapter-php
.NET	cypress-adapter-dotnet

[airhorns]

Are these still a planned feature for cypress or are you folks advocating people make custom endpoints to build integrations?

[Kondasamy]

Do we have any plans to implement these adapters?

[jennifer-shehane]

@Kondasamy No work has been done on this feature. It is still a proposal.

[idxn]

I vote for this and would like to see it in the roadmap

[cmsax]

There's no need to build adapter, because Cypress is a test runner for Javascript based projects with Chrome or Electron as backend browser environment. Cypress itself just makes it easy to launch a browser and encapsulate browsers' API for you to automatically test projects. Chrome | Edge | Firefox driver is enough.

[WTK]

What does that mean in practice though? If I'd like to write cypress.io tests in python would that be an option?

I imagine that one way it could be handled is via python code with similar api to cypress, code that is simply used to generate valid Javascript in the background and run it using usual cypress tools.

[Ambro17]

Is there any news on python adapter? I would like to help as cypress seems to be a great tool and python syntax may really help to increase tests readibility/maintenance

[cypress-zh]

Do u guys have any solution on how to convert cypress js APIs to python version? I'm so interested in this contribution.

[WTK]

I was personally thinking using something like https://github.com/QQuick/Transcript to have an intermediate step of converting python to js and then running it as usual.

Either that or creating a python adapter that would generate compatible spec js files on the fly. Cypress api is rather small, it would be semi easy to create a python code that translates to individual cypress calls.

Edit: and one more approach that already has been tested for other libraries out there: use ruby adapter as a base and port that to python. It definitely sounds easier than coming up with your own structure.

[Vinerhugo]

Ainda estou no aguardo do cypress-adaptor-python seria de extrema ajuda, não estou conseguindo tirar o coverage dos meus testes cypress no meu backend python

[Ambro17]

For anyone looking for a testing framework with first-class support for python you can look at playwright-python
It is maintained by microsoft so support should be guaranteed

[Vinerhugo]

My friend i need integration my code cypress and my back-end Python, you can help-me ? Enviado do Outlook<http://aka.ms/weboutlook>

…

________________________________ De: Ambro <notifications@github.com> Enviado: terça-feira, 25 de agosto de 2020 15:17 Para: cypress-io/cypress <cypress@noreply.github.com> Cc: Vinerhugo <vinerhugo@hotmail.com>; Comment <comment@noreply.github.com> Assunto: Re: [cypress-io/cypress] Backend Adapters (#794) For anyone looking for a testing framework with first-class support for python you can look at playwright-python<https://github.com/microsoft/playwright-python> It is maintained by microsoft so support should be guaranteed — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#794 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHUFNSKHD7QXPTFVVAUH6ADSCQL43ANCNFSM4EAMNMQQ>.

[jennifer-shehane]

Closing as this is no longer under consideration to extend our products in this manner to support backend adapters.

[Ambro17]

Thank you @jennifer-shehane for resolution. Is there any link where we can read about the reasons behind the decision?