-
Type:
Epic
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Astrolabe
-
None
-
Sunset Astrolabe
-
To Do
-
0
-
0
-
0
-
100
-
Needed - No Spec Changes
-
-
None
-
None
-
None
-
None
-
None
-
None
Summary
The client libraries team proposes to sunset the Astrolabe testing framework.
Motivation
Who is the affected end user?
Client libraries engineering is primarily affected, as that team is responsible for troubleshooting frequent failures of the Astrolabe test suite.
However, we should write a scope document to get input from server and Atlas teams, to ensure that they are not relying on this test suite for their own correctness guarantees.
The client libraries team is confident that drivers have sufficient correctness guarantees from other tests, which is why we are comfortable proposing this change.
How does this affect the end user?
N/A
How likely is it that this problem or use case will occur?
N/A
If the problem does occur, what are the consequences and how severe are they?
N/A
Is this issue urgent?
No required timeline. It's not urgent, but investigation of Astrolabe failures are low yield (the issue is never an actual bug), but often tricky to investigate to prove that failures are environment, and to fix those failures in order to get the suite green again.
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
It is test removal
Acceptance Criteria
- split to
-
CDRIVER-5910 Sunset Astrolabe
-
- Blocked
-
-
CSHARP-5509 Sunset Astrolabe
-
- Blocked
-
-
CXX-3230 Sunset Astrolabe
-
- Blocked
-
-
GODRIVER-3490 Sunset Astrolabe
-
- Blocked
-
-
JAVA-5798 Sunset Astrolabe
-
- Blocked
-
-
NODE-6783 Sunset Astrolabe
-
- Blocked
-
-
PHPLIB-1633 Sunset Astrolabe
-
- Blocked
-
-
PYTHON-5152 Sunset Astrolabe
-
- Blocked
-
-
RUBY-3627 Sunset Astrolabe
-
- Blocked
-
-
RUST-2163 Sunset Astrolabe
-
- Blocked
-
-
MOTOR-1436 Sunset Astrolabe
-
- Closed
-