Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Smoke Tests] Service Bus samples have 2 levels and the 2nd level seems to be missing
See original GitHub issueThere are 8 samples at the samples/typescript/src level and 7 more at samples/typescript/src/advanced level.
- Of the 8 samples at the root level, 4 were skipped in package.json.
- The rest 4 are being run, here is a screenshot of the logs from smoke test pipeline.
- The rest 4 are being run, here is a screenshot of the logs from smoke test pipeline.
- None of the 7 samples at the
advanced/level are being run/considered.
pipeline (Microsoft Internal): https://dev.azure.com/azure-sdk/internal/_build?definitionId=740&_a=summary
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
build reliability]: Nightly smoke tests runs are failing ... - GitHub
The JavaScript smoke tests pipeline has been failing for quite some ... and seem to involve samples from form-recognizer and service-bus:.
Read more >Smoke Testing Vs Sanity Testing: Difference with Examples
Explore the Differences between Smoke Testing and Sanity Testing in detail with examples: In this tutorial, you will learn what is Sanity ...
Read more >Smoke Testing Keeps Your Delivery Pipeline Safe and Sound
Smoke testing is a technique for discovering major software flaws using CI/CD pipelines. It consists of very shallow but broad tests that ...
Read more >What is Smoke Testing? - Guru99
SMOKE TESTING is a type of software testing that determines whether the deployed build is stable or not. The purpose of Smoke Tests...
Read more >What is Smoke Testing? | Edureka - YouTube
| Smoke Testing Example | Software Testing Tutorial for Beginners | Edureka.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So, it looks like the advanced samples are now running when I run
npm run execute:samples. The issue blocking this from being closed is https://github.com/Azure/azure-sdk-for-js/issues/16656Since we’ve migrated to v2 samples, the smoke tests aren’t currently running the service bus samples.
Are we really gaining value having the advanced samples in their own subdirectory? I wonder if it makes more sense to have a flat list, and we can weight the advanced samples so they appear at the bottom of the README table.
Otherwise we’ll have to figure out how to update our tooling to support nested samples.