Remove overly complicated test

This commit is contained in:
Brandon Hancock
2024-07-31 10:12:37 -04:00
parent 41df368156
commit 6aab0ebcbc
2 changed files with 1 additions and 7 deletions

View File

@@ -53,7 +53,7 @@ Pipeline Terminology:
- Trace: The journey of an individual input through the entire pipeline. - Trace: The journey of an individual input through the entire pipeline.
Example pipeline structure: Example pipeline structure:
crew1 >> crew2 >> crew3 crew1 >> crew2 >> crew3
This represents a pipeline with three sequential stages: This represents a pipeline with three sequential stages:
1. crew1 is the first stage, which processes the input and passes its output to crew2. 1. crew1 is the first stage, which processes the input and passes its output to crew2.

View File

@@ -334,12 +334,6 @@ async def test_pipeline_with_parallel_stages_end_in_single_stage(mock_crew_facto
assert pipeline_result_1.token_usage == expected_token_usage assert pipeline_result_1.token_usage == expected_token_usage
@pytest.mark.asyncio
async def test_pipeline_with_parallel_stages_multiple_inputs(mock_crew_factory):
# TODO: implement
pass
def test_pipeline_rshift_operator(mock_crew_factory): def test_pipeline_rshift_operator(mock_crew_factory):
""" """
Test that the >> operator correctly creates a Pipeline from Crews and lists of Crews. Test that the >> operator correctly creates a Pipeline from Crews and lists of Crews.