Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update test bots to use cosmos DB #37

Open
gabog opened this issue Apr 17, 2020 · 2 comments
Open

Update test bots to use cosmos DB #37

gabog opened this issue Apr 17, 2020 · 2 comments
Assignees
@gabog
Labels
Area: Functional tests The issue is related to end to end tests backlog The issue is out of scope for the current iteration but it will be evaluated in a future release. draft The issue definition is still being worked on and it is not ready to start development. feature-request A request for new functionality or an enhancement to an existing one. P1 Painful if we don't fix, won't block releasing

Comments

@gabog
Copy link
Contributor

gabog commented Apr 17, 2020

We use MemoryStorage in most of our unit tests in the product and I think it may be better to use cosmosDB for state for end to end testing. It will help us catch serialization and other storage related issues that we don't normally see in our tests based on MemoryStorage (it happened in the past).
@mrivera-ms
Copy link
Contributor

@gabog, would it be good to add a few CosmosDb scenarios instead of updating all existing tests? I have concerns about the time that will take to run all tests if make this change.

@gabog
Copy link
Contributor Author

gabog commented Sep 10, 2020

Can we use an existing cosmosDB instance so we don't have to wait for the resource to be provisioned? All the cosmosDB serialization issues have been addressed as far as we know and I was hoping the functional tests may help us catch new ones that we may introduce in the future.

@gabog gabog self-assigned this Nov 13, 2020
@gabog gabog added feature-request A request for new functionality or an enhancement to an existing one. draft The issue definition is still being worked on and it is not ready to start development. needs-triage The issue has just been created and it has not been reviewed by the team. P0 Must Fix. Release-blocker Area: Functional tests The issue is related to end to end tests labels Nov 13, 2020
@gabog gabog added this to the R12 milestone Nov 13, 2020
@gabog gabog added P1 Painful if we don't fix, won't block releasing and removed P0 Must Fix. Release-blocker labels Nov 19, 2020
@gabog gabog removed this from the R12 milestone Feb 3, 2021
@gabog gabog added backlog The issue is out of scope for the current iteration but it will be evaluated in a future release. and removed needs-triage The issue has just been created and it has not been reviewed by the team. labels Feb 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gabog gabog

Labels
Area: Functional tests The issue is related to end to end tests backlog The issue is out of scope for the current iteration but it will be evaluated in a future release. draft The issue definition is still being worked on and it is not ready to start development. feature-request A request for new functionality or an enhancement to an existing one. P1 Painful if we don't fix, won't block releasing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gabog @mrivera-ms