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.

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

Support expect from different source (RDT-311) #155

Open
5 tasks
hfudev opened this issue Nov 4, 2022 · 0 comments
Open
5 tasks

Support expect from different source (RDT-311) #155

hfudev opened this issue Nov 4, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@hfudev
Copy link
Member

hfudev commented Nov 4, 2022

Now we have a few different sources, like serial, openocd, gdb, ..., etc. Each source is a single process, and would have their own output and input. if we combine all the output from different sources into one single pexpect process, then it would sometimes be messed up.

Success Criteria:

  • Record the output of each process into a single file, and has its own pexpect process.
  • modify the original PexpectProcess class, to make it as the parent class to hold all the processes created by different sources. The users would still use the same API to expect the patterns from different sources.
  • add keyword source of expect functions to indicate which source to expect from. default set to serial.
  • add keyword source of redirect fixture
  • add attr source to all derived fixture classes

and one reminder:

  • don't make breaking changes. it's not necessary.
@hfudev hfudev self-assigned this Nov 4, 2022
@github-actions github-actions bot changed the title Support expect from different source Support expect from different source (RDT-311) Nov 4, 2022
@hfudev hfudev added this to the 1.1.0 milestone Nov 4, 2022
@hfudev hfudev added the enhancement New feature or request label Nov 24, 2022
@hfudev hfudev modified the milestones: 1.x, 2.0.0 Nov 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant