-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
beginner: add coverage #1963
Comments
@mattklein123 Hi, could I pick this one up? |
@minhlongdo this is a "perma issue." Feel free to just go ahead and add some coverage! |
…anslateCors to RdsJson class Risk Level: Low Testing: unit test Release Notes: N/A Fixes #Issue: envoyproxy#1963 Signed-off-by: Andrzej Wawrzyniak <andrzejwaw@gmail.com>
@mattklein123 I went to try my hand at one of these and noticed that the s3 bucket gives an AccessDenied error. Any idea why that may be? |
Sorry the coverage report has moved here: https://storage.googleapis.com/envoy-coverage/report-master/index.html |
@mattklein123 Where can I find the coverage report? Above link gives Edit: Found it at https://storage.googleapis.com/envoy-postsubmit/main/coverage/index.html |
@saiskee clicking that link work for me - not sure what the error you saw was but should work |
apologies - i see now - i clicked the link that you posted - the one that works |
Adding more tests to increase line coverage for json package. Adding coverage for missing code paths by testing various loadFromString inputs. Risk Level: Low Testing: Added tests to json_loader_test Docs Changes: n/a Release Notes: n/a Platform Specific Features: n/a This PR seeks to improve this issue: #1963 Signed-off-by: Tom Hadlaw <tomhadlaw@gmail.com>
Adding more tests to increase line coverage for json package. Adding coverage for missing code paths by testing various loadFromString inputs. Risk Level: Low Testing: Added tests to json_loader_test Docs Changes: n/a Release Notes: n/a Platform Specific Features: n/a This PR seeks to improve this issue: envoyproxy#1963 Signed-off-by: Tom Hadlaw <tomhadlaw@gmail.com> Signed-off-by: Josh Perry <josh.perry@mx.com>
Hi! I would love to help a bit with coverage, but getting access denied on the link above for coverage report. Is help still needed? |
https://storage.googleapis.com/envoy-postsubmit/main/coverage/index.html should be the working URL and I think it's wide open. |
…eamIntel. (#1963) Initial integration on the FinalStreamIntel for Cronvoy Java tests added for Envoy-Mobile and Cronvoy Description: Adapt Cronvoy to onComplete callBack Risk Level: Small Testing: Tests were added for Envoy-Mobile and Cronvoy Docs Changes: N/A Release Notes: N/A Signed-off-by: Charles Le Borgne <cleborgne@google.com> Signed-off-by: JP Simard <jp@jpsim.com>
…eamIntel. (#1963) Initial integration on the FinalStreamIntel for Cronvoy Java tests added for Envoy-Mobile and Cronvoy Description: Adapt Cronvoy to onComplete callBack Risk Level: Small Testing: Tests were added for Envoy-Mobile and Cronvoy Docs Changes: N/A Release Notes: N/A Signed-off-by: Charles Le Borgne <cleborgne@google.com> Signed-off-by: JP Simard <jp@jpsim.com>
Risk Level: Low Testing: a Test added to header_map_impl_test Docs Changes: n/a Release Notes: n/a Platform Specific Features: n/a This PR seeks to improve this issue: envoyproxy#1963 Signed-off-by: Atul Thosar <atulthosar@gmail.com>
This PR seeks to improve this issue: #1963 Signed-off-by: Atul Thosar <atulthosar@gmail.com>
This PR seeks to improve this issue: envoyproxy#1963 Signed-off-by: Atul Thosar <atulthosar@gmail.com> Signed-off-by: asheryer <asheryer@amazon.com>
This PR seeks to improve this issue: envoyproxy#1963 Signed-off-by: Atul Thosar <atulthosar@gmail.com> Signed-off-by: Ryan Eskin <ryan.eskin89@protonmail.com>
Going to leave open a persistent beginner ticket for adding coverage:
https://s3.amazonaws.com/lyft-envoy/coverage/report-master/coverage.html
There are always a few missing things here and there especially regarding random error handling. If you are a beginner this is a great way to learn and do something valuable.
Rough steps:
The text was updated successfully, but these errors were encountered: