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
We'd like to setup a an integration and e2e test framework. We've used Playwright in the past and that seems like a good plan to use unless we run into some major downsides.
It does look like we can write tests in .Net or in TS, it's up to us, I'm not really sure what's best here since testing out frontend seems like it might be best in TS. However testing the .Net API would probably be easiest in .Net since we could use some of our dotnet code to inject testing data directly into the db.
For this issue I'd consider it done when we have 2 tests, one to test the login page:
type in user name and password
click login button
verify landing on user dashboard
and an API test:
call the FLEx projects endpoint, this requires an explicit user and password to be passed in.
Verify some results
we also at some point want a test for S&R but that can be tracked in #32 as it's a bigger task to tackle.
The text was updated successfully, but these errors were encountered:
Classic site's E2E tests has several Page base classes that, among other things, used a selector after nav to ensure that you really did land on the page that you were trying to navigate to. Copying that approach might serve us well as we get started here.
We'd like to setup a an integration and e2e test framework. We've used Playwright in the past and that seems like a good plan to use unless we run into some major downsides.
It does look like we can write tests in .Net or in TS, it's up to us, I'm not really sure what's best here since testing out frontend seems like it might be best in TS. However testing the .Net API would probably be easiest in .Net since we could use some of our dotnet code to inject testing data directly into the db.
For this issue I'd consider it done when we have 2 tests, one to test the login page:
and an API test:
we also at some point want a test for S&R but that can be tracked in #32 as it's a bigger task to tackle.
The text was updated successfully, but these errors were encountered: