apache/openwhisk

Update CLI scala tests to conform to best practice naming

Open

#2464 opened on Jul 7, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Scala (6,777 stars) (1,177 forks)batch import
enhancementhelp wantedtesting

Description

Scala naming best practice reference: http://docs.scala-lang.org/style/naming-conventions.html

Existing wsk CLI scala tests are not consistent in the use of camel case labels. Also avoid underscores (_) in labels.

Contributor guide

Tech stack
scala
Domain
testingcli
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Scala knowledgeUnderstanding of the Scala naming conventions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The issue requires updating CLI Scala test names to follow Scala naming conventions: use camelCase and avoid underscores. First, locate all Scala test files under the CLI test directory (likely in the OpenWhisk repository under `tests/cli/` or similar). Then, identify test names (e.g., function names or test case labels) that violate the convention. Rename them according to the linked style guide. No additional changes beyond naming are needed. No linked PRs or comments, so no external dependencies.