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.

Sign up for GitHub

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

Jump to bottom

Missing non-dependent browser integration test for botframework-streaming #2440

Open
3 tasks
stevengum opened this issue Jun 28, 2020 · 1 comment
Open
3 tasks

Missing non-dependent browser integration test for botframework-streaming #2440

stevengum opened this issue Jun 28, 2020 · 1 comment
Labels
Area: Engineering Internal issues that are related to improving code quality, refactorings, code cleanup, etc. backlog The issue is out of scope for the current iteration but it will be evaluated in a future release. P2 Nice to have Size: L The issue is complex but it is well understood, it will take 4 to 8 days to complete
Projects
Engineering Testing

Comments

@stevengum
Copy link
Member

Describe the bug

botframework-streaming should have its own browser integration tests that are not reliant on any dependent libraries (e.g. botframework-directlinejs, botframework-webchat) or dependent's tool chains.

Expected behavior

  • browser-based app using botframework-streaming should build
    • without/with the use of browserify, parcel, rollup, webpack
  • no runtime errors in app from botframework-streaming
tool test exists?
nothing ❌
browserify ❌
parcel ❌
rollup ❌
webpack ❌

[bug]
@stevengum stevengum added P0 Must Fix. Release-blocker R10 Release 10 - August 17th, 2020 BF Agility For Issues or Feature Requests that impact the SDK Team's agility labels Jun 28, 2020
@stevengum stevengum self-assigned this Jun 28, 2020
@munozemilio munozemilio added this to the R10 milestone Jul 1, 2020
@stevengum stevengum removed this from the R10 milestone Aug 4, 2020
@stevengum stevengum added Area: Engineering Internal issues that are related to improving code quality, refactorings, code cleanup, etc. R11 and removed R10 Release 10 - August 17th, 2020 labels Aug 4, 2020
@gabog gabog added this to the R11 milestone Sep 2, 2020
@gabog gabog removed the R11 label Sep 2, 2020
@stevengum stevengum removed this from the R11 milestone Oct 5, 2020
@stevengum stevengum added backlog The issue is out of scope for the current iteration but it will be evaluated in a future release. and removed BF Agility For Issues or Feature Requests that impact the SDK Team's agility P0 Must Fix. Release-blocker labels Oct 5, 2020
@stevengum
Copy link
Member Author

With the current CI configuration and streaming E2E test, this is no longer a P0 and has been placed on the backlog for now.

@joshgummersall joshgummersall added this to the R12 milestone Nov 4, 2020
@joshgummersall joshgummersall added P2 Nice to have Size: L The issue is complex but it is well understood, it will take 4 to 8 days to complete and removed backlog The issue is out of scope for the current iteration but it will be evaluated in a future release. labels Nov 4, 2020
@joshgummersall joshgummersall added this to To do in Engineering Jan 14, 2021
@joshgummersall joshgummersall removed this from the R12 milestone Jan 27, 2021
@joshgummersall joshgummersall added the backlog The issue is out of scope for the current iteration but it will be evaluated in a future release. label Apr 6, 2021
@joshgummersall joshgummersall added this to To do in Testing via automation May 13, 2021
@mrivera-ms mrivera-ms assigned msomanathan and unassigned stevengum Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Engineering Internal issues that are related to improving code quality, refactorings, code cleanup, etc. backlog The issue is out of scope for the current iteration but it will be evaluated in a future release. P2 Nice to have Size: L The issue is complex but it is well understood, it will take 4 to 8 days to complete
Projects
Engineering
  
To do
Testing
  
To do
Milestone
No milestone
Development

No branches or pull requests
5 participants
@joshgummersall @gabog @stevengum @msomanathan @munozemilio