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
{{ message }}
This repository has been archived by the owner on Oct 12, 2021. It is now read-only.
As a Shunting Yard developer I'd like to make sure that the code in master is correctly integrated with the infrastructure So I can ensure the application behaves as expected in runtime
Overview
At the moment we don't have a test suite to guaranty that correct behavior of Shunting Yard at runtime. This is critical for a service of this nature and we must do the best possible to avoid releasing critical bugs that may have been introduced during the coding phase.
Acceptance Criteria
New project with the integration test bed
The new project must be deployable to AWS
Basic cases that include the whole lifecycle of a partitioned and unpartitioned tables:
** Partitioned table: create table, add partition, update partition, update table cascade, drop partition, drop table
** Unpartitioned table: create table, update table, drop table
Include edge cases:
** Update/drop a table that does not exist in the replica
** Update/drop a partition that does not exist in the replica
** Create a table that already exists in the replica
** Create a partition that already exists in the replica
** Others
The text was updated successfully, but these errors were encountered:
As a Shunting Yard developer
I'd like to make sure that the code in master is correctly integrated with the infrastructure
So I can ensure the application behaves as expected in runtime
Overview
At the moment we don't have a test suite to guaranty that correct behavior of Shunting Yard at runtime. This is critical for a service of this nature and we must do the best possible to avoid releasing critical bugs that may have been introduced during the coding phase.
Acceptance Criteria
** Partitioned table: create table, add partition, update partition, update table cascade, drop partition, drop table
** Unpartitioned table: create table, update table, drop table
** Update/drop a table that does not exist in the replica
** Update/drop a partition that does not exist in the replica
** Create a table that already exists in the replica
** Create a partition that already exists in the replica
** Others
The text was updated successfully, but these errors were encountered: