Python Trajectories
Second trajectory: Patch Trajectory First trajectory: Test Patch Trajectory
! The Patch trajectory is independent
from the 'Test Patch' trajectory
Start Start
Carefully read, interpret, and dissect problem Carefully read, interpret, and dissect problem
statement. statement.
Analyze related discussions and documentation
! Tasks are provided with an associated
GitHub pull-request. There you will find
a discussion regarding the problem
Analyze related discussions and documentation
Run the test command in the terminal and
determine the testing situation. Does the problem
Run the test(s) from the "Run Tests" button and carefully read and statement mention if there are test(s) present
analyze the output
Write a thought in the run test step to explain how
Write a thought in the run test step to explain how you understand you understand the task, what the goal is, and how
the task, what the goal is, and how you initially plan to approach the you initially plan to approach the investigation
investigation
! Knowledge from the test patch should
not be mentioned in the thoughts
Carefully navigate through the codebase using knowledge from the
test patch stage making sure the actions and thoughts progress
logically. No tests present
Are there test
present?
Partial tests present
Run tests command on the terminal, analyze
the output and confirm the lack of a test
Identify and mention relevant files, lines, error and log messages in recreates the issue
the thoughts of the navigation steps.
Write a thought in the open step in which you include your Check existing tests.
observation, action plan, immediate action, and
expectation/hypothesis mainly regarding what made you open that
file.
Is there a test
present that recreates Yes
the issue?
Make appropriate edits and include thoughts in those edit steps
describing your observations, actions plan, immediate action, and No
expectation/hypothesis. Are the tests good and The tests are good and but
Write a thought in the open file step The tests comprehensive
Locate a test file where the new test case explaining why the test(s) where not are not good are not comprehensive
Write a thought in the edit step in which you include your
observation, action plan, immediate action, and would best fit. If none are suitable, create a sufficient
expectation/hypothesis new test file to place the test login inside.
The tests are good
Write F2P (Failure-to-pass) test logic and comprehensive
Enhance/modify the relevant test(s) -one
Run the tests from the "Run Tests" button and check whether or not that fails in the presence of the bug.
the issue has been solved.
Write a thought in the step where you edited
Run the test command on the terminal and the test(s) explaining why the tests required
Run the test command on the terminal confirm it reproduces the issue an edit
Write a thought in the command action step
explaining why the tests were sufficient
Do the test(s)
The test(s) fail to pass
pass?
Do the test(s)
No, the issue was reproduce the issue
not reproduced correctly ?
The test(s) successfuly pass Run the test command and confirm it
Yes, the issue was reproduces the issue
reproduced
Start patch trajectory. (The test patch
End patch trajectory trajectory should be finalized after the patch
trajectory have been completed)
End test patch trajectory
Submit task