test: increase code coverage in blas/base/caxpy

[ShabiShett07]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: na
• task: lint_package_json status: na
• task: lint_repl_help status: na
• task: lint_javascript_src status: na
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: na
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: na
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: na
• task: lint_typescript_tests status: na
• task: lint_license_headers status: passed ---

none

Description

What is the purpose of this pull request?

This pull request:

• adds test cases for blas/base/caxpy which had an incomplete coverage report.

Related Issues

Does this pull request have any related issues?

This pull request:

• none

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/base/caxpy	$\color{green}368/368$ $\color{green}+100.00\%$	$\color{green}17/17$ $\color{green}+100.00\%$	$\color{green}4/4$ $\color{green}+100.00\%$	$\color{green}368/368$ $\color{green}+100.00\%$

The above coverage report was generated for the changes in this PR.

[kgryte]

Thanks, @ShabiShett07. Just a note that native add-on tests require an opts argument to ensure that we only attempt to run tests when a *.node file have been built.

[kgryte]

BTW: @ShabiShett07 You should be keeping your local develop branch more up-to-date with the current upstream develop of this repo. Your branch was 812 commits behind, and it is possible we'll have fixed tooling regressions, etc, during the interim.

[kgryte]

See our Git cheatsheet for more info.

[ShabiShett07]

BTW: @ShabiShett07 You should be keeping your local develop branch more up-to-date with the current upstream develop of this repo. Your branch was 812 commits behind, and it is possible we'll have fixed tooling regressions, etc, during the winter
Sorry for that, I will ensure this from now on