diff --git a/config.json b/config.json index 60b0187e..6d40e34d 100644 --- a/config.json +++ b/config.json @@ -313,6 +313,14 @@ "prerequisites": [], "difficulty": 3 }, + { + "slug": "binary-search", + "name": "Binary Search", + "uuid": "4a580b6d-a370-4526-a5ea-d7c856279676", + "practices": [], + "prerequisites": [], + "difficulty": 3 + }, { "slug": "pascals-triangle", "name": "Pascal's Triangle", diff --git a/exercises/practice/binary-search/.docs/instructions.md b/exercises/practice/binary-search/.docs/instructions.md new file mode 100644 index 00000000..ae45210e --- /dev/null +++ b/exercises/practice/binary-search/.docs/instructions.md @@ -0,0 +1,36 @@ +# Instructions + +Implement a binary search algorithm. Do not use any COBOL proprietary +search routines (eg. SEARCH). + +Searching a sorted collection is a common task. A dictionary is a sorted +list of word definitions. Given a word, one can find its definition. A +telephone book is a sorted list of people's names, addresses, and +telephone numbers. Knowing someone's name allows one to quickly find +their telephone number and address. + +If the list to be searched contains more than a few items (a dozen, say) +a binary search will require far fewer comparisons than a linear search, +but it imposes the requirement that the list be sorted. + +In computer science, a binary search or half-interval search algorithm +finds the position of a specified input value (the search "key") within +an array sorted by key value. + +In each step, the algorithm compares the search key value with the key +value of the middle element of the array. + +If the keys match, then a matching element has been found and its index, +or position, is returned. + +Otherwise, if the search key is less than the middle element's key, then +the algorithm repeats its action on the sub-array to the left of the +middle element or, if the search key is greater, on the sub-array to the +right. + +If the remaining array to be searched is empty, then the key cannot be +found in the array and a special "not found" indication is returned. + +A binary search halves the number of items to check with each iteration, +so locating an item (or determining its absence) takes logarithmic time. +A binary search is a dichotomic divide and conquer search algorithm. diff --git a/exercises/practice/binary-search/.docs/introduction.md b/exercises/practice/binary-search/.docs/introduction.md new file mode 100644 index 00000000..d998c9e8 --- /dev/null +++ b/exercises/practice/binary-search/.docs/introduction.md @@ -0,0 +1,35 @@ +# Introduction + +Implement a binary search algorithm. + +Searching a sorted collection is a common task. A dictionary is a sorted +list of word definitions. Given a word, one can find its definition. A +telephone book is a sorted list of people's names, addresses, and +telephone numbers. Knowing someone's name allows one to quickly find +their telephone number and address. + +If the list to be searched contains more than a few items (a dozen, say) +a binary search will require far fewer comparisons than a linear search, +but it imposes the requirement that the list be sorted. + +In computer science, a binary search or half-interval search algorithm +finds the position of a specified input value (the search "key") within +an array sorted by key value. + +In each step, the algorithm compares the search key value with the key +value of the middle element of the array. + +If the keys match, then a matching element has been found and its index, +or position, is returned. + +Otherwise, if the search key is less than the middle element's key, then +the algorithm repeats its action on the sub-array to the left of the +middle element or, if the search key is greater, on the sub-array to the +right. + +If the remaining array to be searched is empty, then the key cannot be +found in the array and a special "not found" indication is returned. + +A binary search halves the number of items to check with each iteration, +so locating an item (or determining its absence) takes logarithmic time. +A binary search is a dichotomic divide and conquer search algorithm. diff --git a/exercises/practice/binary-search/.meta/config.json b/exercises/practice/binary-search/.meta/config.json new file mode 100644 index 00000000..11bbddab --- /dev/null +++ b/exercises/practice/binary-search/.meta/config.json @@ -0,0 +1,23 @@ +{ + "authors": [ + "kapitaali" + ], + "files": { + "solution": [ + "src/binary-search.cob" + ], + "test": [ + "tst/binary-search/binary-search.cut" + ], + "example": [ + ".meta/proof.ci.cob" + ], + "invalidator": [ + "test.sh", + "test.ps1" + ] + }, + "blurb": "Implement a binary search algorithm.", + "source": "Wikipedia", + "source_url": "http://en.wikipedia.org/wiki/Binary_search_algorithm" +} diff --git a/exercises/practice/binary-search/.meta/proof.ci.cob b/exercises/practice/binary-search/.meta/proof.ci.cob new file mode 100644 index 00000000..73c99d60 --- /dev/null +++ b/exercises/practice/binary-search/.meta/proof.ci.cob @@ -0,0 +1,106 @@ + IDENTIFICATION DIVISION. + PROGRAM-ID. BINARY-SEARCH. + AUTHOR. kapitaali. + ENVIRONMENT DIVISION. + DATA DIVISION. + WORKING-STORAGE SECTION. + 01 WS-ITEM PIC 9999. + 01 WS-RESULT PIC 9999. + 01 WS-ERROR PIC X(40) VALUE SPACES. + 01 WS-ARRAY PIC X(60). + 01 L PIC 99 VALUE 0. + 01 R PIC 99. + 01 M PIC 99. + 01 STR PIC X(60). + 01 EXP PIC 999 VALUE ZEROES. + 01 IDX PIC 999. + 01 NUM2 PIC ZZ9 VALUE ZEROES. + 01 COUNTER PIC 999. + 01 LEN PIC 999. + + 01 Teibel. + 02 Taulukko PIC 999 OCCURS 1 TO 20 + DEPENDING ON IDX. + + PROCEDURE DIVISION. + + STR-LENGTH. + MOVE 0 TO LEN. + PERFORM VARYING COUNTER FROM FUNCTION LENGTH(STR) + BY -1 UNTIL STR(COUNTER:1) <> " " + ADD 1 TO LEN + END-PERFORM. + COMPUTE LEN = FUNCTION LENGTH(STR) - LEN. + + + REVERSE-TABLE. + COMPUTE R = FUNCTION INTEGER-PART(IDX / 2). + PERFORM VARYING COUNTER FROM 1 BY 1 UNTIL COUNTER = R + COMPUTE L = IDX - COUNTER + MOVE Taulukko(L) TO NUM2 + MOVE Taulukko(COUNTER) TO Taulukko(L) + MOVE NUM2 TO Taulukko(COUNTER) + END-PERFORM. + + + * populates the table from input string + MOVE-TO-TABLE. + MOVE WS-ARRAY TO STR. + PERFORM STR-LENGTH. + MOVE 20 TO IDX. + INITIALIZE Teibel. + MOVE 3 TO EXP. + MOVE 1 TO IDX + MOVE ZEROES TO NUM2. + PERFORM VARYING COUNTER FROM LEN BY -1 UNTIL COUNTER = 0 + IF WS-ARRAY(COUNTER:1) = ',' + MOVE 3 TO EXP + MOVE NUM2 TO Taulukko(IDX) + MOVE ZEROES TO NUM2 + ADD 1 TO IDX + ELSE IF COUNTER = 1 + MOVE WS-ARRAY(COUNTER:1) TO NUM2(EXP:1) + MOVE NUM2 TO Taulukko(IDX) + ADD 1 TO IDX + ELSE + MOVE WS-ARRAY(COUNTER:1) TO NUM2(EXP:1) + SUBTRACT 1 FROM EXP + END-IF + END-PERFORM. + + * the actual algorithm + BINARY-SEARCH. + MOVE ZERO TO WS-RESULT. + MOVE SPACES TO WS-ERROR. + PERFORM MOVE-TO-TABLE. + IF IDX > 2 + PERFORM REVERSE-TABLE + END-IF. + IF L IS LESS THAN 1 OR R IS GREATER THAN IDX + MOVE "value not in array" TO WS-ERROR + EXIT PROGRAM + END-IF. + MOVE 1 TO L. + COMPUTE R = IDX - 1. + PERFORM UNTIL L IS GREATER THAN R + COMPUTE M = L + R + COMPUTE M = FUNCTION INTEGER-PART(M / 2) + IF Taulukko(M) = WS-ITEM + MOVE M TO WS-RESULT + EXIT PARAGRAPH + END-IF + IF Taulukko(M) IS LESS THAN WS-ITEM + COMPUTE L = M + 1 + ELSE IF Taulukko(M) IS GREATER THAN WS-ITEM + COMPUTE R = M - 1 + ELSE + COMPUTE WS-RESULT = M - 1 + IF Taulukko(WS-RESULT) = WS-ITEM + EXIT PROGRAM + ELSE + MOVE "value not in array" TO WS-ERROR + EXIT PROGRAM + END-IF + END-IF + END-PERFORM. + MOVE "value not in array" TO WS-ERROR. diff --git a/exercises/practice/binary-search/bin/fetch-cobolcheck b/exercises/practice/binary-search/bin/fetch-cobolcheck new file mode 100755 index 00000000..64230fe2 --- /dev/null +++ b/exercises/practice/binary-search/bin/fetch-cobolcheck @@ -0,0 +1,63 @@ +#!/usr/bin/env bash + +# This file is a copy of the +# https://github.com/exercism/configlet/blob/main/scripts/fetch-configlet file. +# Please submit bugfixes/improvements to the above file to ensure that all tracks benefit from the changes. + +# set -eo pipefail + +readonly LATEST='https://api.github.com/repos/0xE282B0/cobol-check/releases/latest' + +case "$(uname)" in + Darwin*) os='mac' ;; + Linux*) os='linux' ;; + Windows*) os='windows' ;; + MINGW*) os='windows' ;; + MSYS_NT-*) os='windows' ;; + *) os='linux' ;; +esac + +case "${os}" in + windows*) ext='.exe' ;; + *) ext='' ;; +esac + +arch="$(uname -m)" + +curlopts=( + --silent + --show-error + --fail + --location + --retry 3 +) + +if [[ -n "${GITHUB_TOKEN}" ]]; then + curlopts+=(--header "authorization: Bearer ${GITHUB_TOKEN}") +fi + +suffix="${os}-${arch}${ext}" + +get_download_url() { + curl "${curlopts[@]}" --header 'Accept: application/vnd.github.v3+json' "${LATEST}" | + grep "\"browser_download_url\": \".*/download/.*/cobol-check.*${suffix}\"$" | + cut -d'"' -f4 +} + +main() { + if [[ -d ./bin ]]; then + output_dir="./bin" + elif [[ $PWD == */bin ]]; then + output_dir="$PWD" + else + echo "Error: no ./bin directory found. This script should be ran from a repo root." >&2 + return 1 + fi + + output_path="${output_dir}/cobolcheck${ext}" + download_url="$(get_download_url)" + curl "${curlopts[@]}" --output "${output_path}" "${download_url}" + chmod +x "${output_path}" +} + +main diff --git a/exercises/practice/binary-search/bin/fetch-cobolcheck.ps1 b/exercises/practice/binary-search/bin/fetch-cobolcheck.ps1 new file mode 100644 index 00000000..261f5f45 --- /dev/null +++ b/exercises/practice/binary-search/bin/fetch-cobolcheck.ps1 @@ -0,0 +1,28 @@ +# This file is a copy of the +# https://github.com/exercism/configlet/blob/main/scripts/fetch-configlet.ps1 file. +# Please submit bugfixes/improvements to the above file to ensure that all tracks +# benefit from the changes. + +$ErrorActionPreference = "Stop" +$ProgressPreference = "SilentlyContinue" + +$requestOpts = @{ + Headers = If ($env:GITHUB_TOKEN) { @{ Authorization = "Bearer ${env:GITHUB_TOKEN}" } } Else { @{ } } + MaximumRetryCount = 3 + RetryIntervalSec = 1 +} + +$arch = If ([Environment]::Is64BitOperatingSystem) { "amd64" } Else { "x86" } +$fileName = "cobol-check-windows-$arch.exe" + +Function Get-DownloadUrl { + $latestUrl = "https://api.github.com/repos/0xE282B0/cobol-check/releases/latest" + Invoke-RestMethod -Uri $latestUrl -PreserveAuthorizationOnRedirect @requestOpts + | Select-Object -ExpandProperty assets + | Where-Object { $_.browser_download_url -match $FileName } + | Select-Object -ExpandProperty browser_download_url +} + +$downloadUrl = Get-DownloadUrl +$outputFile = Join-Path -Path $PSScriptRoot -ChildPath "cobolcheck.exe" +Invoke-WebRequest -Uri $downloadUrl -OutFile $outputFile @requestOpts \ No newline at end of file diff --git a/exercises/practice/binary-search/config.properties b/exercises/practice/binary-search/config.properties new file mode 100644 index 00000000..2c5a6c8e --- /dev/null +++ b/exercises/practice/binary-search/config.properties @@ -0,0 +1,183 @@ +# Configuration settings for Cobol Check + +#--------------------------------------------------------------------------------------------------------------------- +# This configuration - echoed to console when Cobol Check is executed, for information only. +#--------------------------------------------------------------------------------------------------------------------- +config.loaded = production + +#--------------------------------------------------------------------------------------------------------------------- +# Prefix for field names and paragraph names in the test management code that cobol-check +# inserts into programs to be tested. The default is "UT-". If this conflicts with names +# in the programs to be tested, you can override it with a value you specify here. +# The value must be 3 characters or less. Cannot be empty. +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.prefix = UT- + +#--------------------------------------------------------------------------------------------------------------------- +# Tags written in the generated test code in the form of a comment, when a code injection starts and ends. +# Default is null, which will prevent the tags from appearing. Any other value will appear as comments +# surrounding the injected code. +# Examples: +# cobolcheck.injectedCodeTag.start = ###INJECT START### +# cobolcheck.injectedCodeTag.end = ###INJECT END### +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.injectedCodeTag.start = null +cobolcheck.injectedCodeTag.end = null + +#--------------------------------------------------------------------------------------------------------------------- +# A tag written at the start of entities stubbed by default. Recommended value-length <= 4. +# Note: The tag will appear only when cobolcheck stubs lines by default. +# This is the case for CALLs and batch file IO verbs. +# Default is null, which will prevent the tag from appearing. +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.stub.comment.tag = null + +#--------------------------------------------------------------------------------------------------------------------- +# Determines if cobolcheck should generate code, such that decimal point is comma. +# The default is "false". The value should be set to "true" if the compiler is set to +# read decimal points as commas. If the cobol source program sets DECIMAL-POINT IS COMMA, +# this configuration will be overwritten. +# Example: 1,385,481.00 (decimalPointIsComma = false) +# Example: 1.385.481,00 (decimalPointIsComma = true) +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.decimalPointIsComma = false + +#--------------------------------------------------------------------------------------------------------------------- +# If the source program contains rules as the first line follwed by CBL, the given value will be appended +# to this. +# If no CBL is found in source, it will be added along with the given value +# default is null, which will make no changes. +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.append.rules = null + +#--------------------------------------------------------------------------------------------------------------------- +# Path for the generated Cobol test code +# Default: ./ +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.test.program.path = ./ + +#--------------------------------------------------------------------------------------------------------------------- +# Suffix to append to the name of each program under test to produce the name of the corresponding +# test program that contains the merged test code. +# Example: For program ABCXYZ4, if suffix is T.CBL then the test program name will be ABCXYZ4T.CBL. +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.test.program.name = test.cob + +#--------------------------------------------------------------------------------------------------------------------- +# Path for the generated testsuite parse error log +# Default: ./ +#--------------------------------------------------------------------------------------------------------------------- +testsuite.parser.error.log.path = ./ + +#--------------------------------------------------------------------------------------------------------------------- +# Name of the generated testsuite parse error log file - with extension +# Default: ParserErrorLog.txt +#--------------------------------------------------------------------------------------------------------------------- +testsuite.parser.error.log.name = ParserErrorLog.txt + +#--------------------------------------------------------------------------------------------------------------------- +# The charset that cobolcheck will use when reading- and writing to files. +# See https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html, for a list of +# valid values. +# Default value for each OS is , which will use the default encoding for the OS. +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.file.encoding.linux = default +cobolcheck.file.encoding.macosx = default +cobolcheck.file.encoding.windows = default +cobolcheck.file.encoding.zos = default +cobolcheck.file.encoding.unix = default + +#--------------------------------------------------------------------------------------------------------------------- +# Sets permissions for all files generated by Cobol Check, for all users. +# If read, write and execute permissions are set, all users can perform said actions on all files +# that Cobol Check generates. +# Value can be any permutation of the letters: 'rwx' (read, write, execute) or none - meaning no permissions. +# Default value: rx +#--------------------------------------------------------------------------------------------------------------------- +generated.files.permission.all = rx + +#--------------------------------------------------------------------------------------------------------------------- +# Determines if Cobol Check should run the generated test program. +# Default is true. +# If set to false, Cobol Check will generate the code, but not run it. If more than one program +# is given as a command line option, the generated test file will be overwritten. Thus if set to false, +# only one program should be given at a time. +#--------------------------------------------------------------------------------------------------------------------- +cobolcheck.test.run = false + +#--------------------------------------------------------------------------------------------------------------------- +# These settings are to locate the application code under test in *your* Cobol project directory tree. +# Can be absolute path or relative to project root. +#--------------------------------------------------------------------------------------------------------------------- +application.source.directory = src +application.copybook.directory = cpy + +#--------------------------------------------------------------------------------------------------------------------- +# Location of test suite input file(s). This can also be passed on command-line option --test-suite-path. +#--------------------------------------------------------------------------------------------------------------------- +test.suite.directory = tst + +#--------------------------------------------------------------------------------------------------------------------- +# Location of test output. File extension is determined by a given format. +#--------------------------------------------------------------------------------------------------------------------- +test.results.file = output/testResults + +#--------------------------------------------------------------------------------------------------------------------- +# Determines the format of the test results written to the output file. +# Supported formats: txt, xml, html. +#--------------------------------------------------------------------------------------------------------------------- +test.results.format = txt + +#--------------------------------------------------------------------------------------------------------------------- +# Determines the format style of the test results written to the output file. +# The style controls the hierarchy and structure of data and naming of the 'object' that is written +# in a given format. Format: txt and style: directOutput are exclusive. txt cannot use any other style +# than directOutput, and directOutput cannot be used with any other format than txt. +# Other formats and styles can be used interchangeably. +# Supported styles: directOutput, JUnit, tableDocument, tableEmbed +#--------------------------------------------------------------------------------------------------------------------- +test.results.format.style = directOutput + +#--------------------------------------------------------------------------------------------------------------------- +# If application source filenames have a suffix, specify it here without the period or dot. +#--------------------------------------------------------------------------------------------------------------------- +application.source.filename.suffix = CBL,cbl,COB,cob + +#--------------------------------------------------------------------------------------------------------------------- +# If application copybook filenames have a suffix, specify it here without the period or dot +# e.g. application.copybook.filename.suffix = CBL +#--------------------------------------------------------------------------------------------------------------------- +application.copybook.filename.suffix = CBL,cbl,COB,cob + +#--------------------------------------------------------------------------------------------------------------------- +# Optional override of system default Locale for log messages and exception messages. +#--------------------------------------------------------------------------------------------------------------------- +#locale.language = ja +#locale.country = +#locale.variant = + +#--------------------------------------------------------------------------------------------------------------------- +# Cobol Check concatenates multiple test suite input files into a single file for the Generator. +# This is the relative or absolute path of the concatenated file. If not specified, the default +# is "./ALLTESTS" relative to the directory in which Cobol Check was started. +#--------------------------------------------------------------------------------------------------------------------- +concatenated.test.suites = ./ALLTESTS + +#--------------------------------------------------------------------------------------------------------------------- +# Shell scripts and JCL files for executing your test suites. +# Cobol Check will invoke one of these after creating the copy of the program under test that contains +# test code generated from your test suites. +# Unix and Mac OS X are both treated as unix. Most unices can run the linux script. +# Unix is the default. +# You can write custom scripts/JCL for your environment, for instance if you are using a different Cobol compiler. +# The first element in these names reflects the first few characters returned by Java's System.getProperty("os.name"). +# Cobol Check will select one of these entries based on which platform it thinks it's running on. +#--------------------------------------------------------------------------------------------------------------------- + +cobolcheck.script.directory = scripts +linux.process = linux_gnucobol_run_tests +osx.process = linux_gnucobol_run_tests +freebsd.process = linux_gnucobol_run_tests +windows.process = windows_gnucobol_run_tests.cmd +zos.process = +unix.process = linux_gnucobol_run_tests diff --git a/exercises/practice/binary-search/src/binary-search.cob b/exercises/practice/binary-search/src/binary-search.cob new file mode 100644 index 00000000..c86c19c5 --- /dev/null +++ b/exercises/practice/binary-search/src/binary-search.cob @@ -0,0 +1,16 @@ + IDENTIFICATION DIVISION. + PROGRAM-ID. BINARY-SEARCH. + ENVIRONMENT DIVISION. + DATA DIVISION. + WORKING-STORAGE SECTION. + 01 WS-ITEM PIC 9999. + 01 WS-RESULT PIC 99. + 01 WS-ERROR PIC X(40). + 01 WS-COUNT PIC 99. + 01 WS-ARRAY-TABLE. + 02 WS-ARRAY OCCURS 1 TO 20 DEPENDING ON WS-COUNT. + 05 ROWELEM PIC 9(4). + + PROCEDURE DIVISION. + + BINARY-SEARCH. diff --git a/exercises/practice/binary-search/test.ps1 b/exercises/practice/binary-search/test.ps1 new file mode 100644 index 00000000..ccfa530a --- /dev/null +++ b/exercises/practice/binary-search/test.ps1 @@ -0,0 +1,16 @@ +$slug=Split-Path $PSScriptRoot -Leaf + +if (![System.IO.File]::Exists("$PSScriptRoot\bin\cobolcheck.exe")){ + Write-Output "Cobolcheck not found. Trying to fetch it." + & "$PSScriptRoot\bin\fetch-cobolcheck.ps1" +} + +Write-Output "Run cobolcheck." +Set-Location $PSScriptRoot + +Invoke-Expression "bin\cobolcheck.exe -p $slug" +Invoke-Expression "cobc -xj test.cob" + +if ($Lastexitcode -ne 0) { + exit $Lastexitcode +} diff --git a/exercises/practice/binary-search/test.sh b/exercises/practice/binary-search/test.sh new file mode 100755 index 00000000..ed4a27a1 --- /dev/null +++ b/exercises/practice/binary-search/test.sh @@ -0,0 +1,20 @@ +#!/usr/bin/env bash +SCRIPT_DIR=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )/ +SLUG=${1:-$(basename "${SCRIPT_DIR}")} +COBOLCHECK=./bin/cobolcheck + +WHICH_COBOLCHECK=$(which cobolcheck) +if [[ $? -eq 0 ]] ; then + echo "Found cobolcheck, using $COBOLCHECK" + COBOLCHECK=$WHICH_COBOLCHECK +elif [ ! -f $SCRIPT_DIR/bin/cobolcheck ]; then + echo "Cobolcheck not found, try to fetch it." + cd $SCRIPT_DIR/bin/ + bash fetch-cobolcheck +fi +cd $SCRIPT_DIR +$COBOLCHECK -p $SLUG + +# compile and run +echo "COMPILE AND RUN TEST" +cobc -xj test.cob diff --git a/exercises/practice/binary-search/tst/binary-search/binary-search.cut b/exercises/practice/binary-search/tst/binary-search/binary-search.cut new file mode 100644 index 00000000..bcc06074 --- /dev/null +++ b/exercises/practice/binary-search/tst/binary-search/binary-search.cut @@ -0,0 +1,76 @@ +TestCase "finds a value in an array with one element" + MOVE "6" TO WS-ARRAY + MOVE 6 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-RESULT = 1 + + +TestCase "finds a value in the middle of an array" + MOVE "1,3,4,6,8,9,11" TO WS-ARRAY + MOVE 6 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-RESULT = 4 + + +TestCase "finds a value in the beginning of an array" + MOVE "1,3,4,6,8,9,11" TO WS-ARRAY + MOVE 1 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-RESULT = 1 + + +TestCase "finds a value at the end of an array" + MOVE "1,3,4,6,8,9,11" TO WS-ARRAY + MOVE 11 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-RESULT = 7 + + +TestCase "finds a value in an array of odd length" + MOVE "1,3,5,8,13,21,34,55,89,144,233,377,634" TO WS-ARRAY + MOVE 144 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-RESULT = 10 + + +TestCase "finds a value in an array of even length" + MOVE "1,3,5,8,13,21,34,55,89,144,233,377,634" TO WS-ARRAY + MOVE 21 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-RESULT = 6 + + +TestCase "finds a value in an array of even length" + MOVE "1,3,4,6,8,9,11" TO WS-ARRAY + MOVE 7 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-ERROR = "value not in array" + + +TestCase "a value smaller than the array's smallest value is not found" + MOVE "1,3,4,6,8,9,11" TO WS-ARRAY + MOVE 0 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-ERROR = "value not in array" + + +TestCase "a value larger than the array's largest value is not found" + MOVE "1,3,4,6,8,9,11" TO WS-ARRAY + MOVE 13 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-ERROR = "value not in array" + + +TestCase "nothing is found in an empty array" + MOVE " " TO WS-ARRAY + MOVE 1 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-ERROR = "value not in array" + + +TestCase "nothing is found when the left and right bounds cross" + MOVE "1,2" TO WS-ARRAY + MOVE 0 TO WS-ITEM + PERFORM BINARY-SEARCH + EXPECT WS-ERROR = "value not in array" + diff --git a/exercises/practice/protein-translation/tst/protein-translation/protein-translation.cut b/exercises/practice/protein-translation/tst/protein-translation/protein-translation.cut index 2ecb299e..2ee609c0 100644 --- a/exercises/practice/protein-translation/tst/protein-translation/protein-translation.cut +++ b/exercises/practice/protein-translation/tst/protein-translation/protein-translation.cut @@ -1,5 +1,5 @@ TestCase "Empty RNA sequence results in no proteins" - MOVE " " TO WS-INPUT + MOVE SPACES TO WS-INPUT PERFORM TRANSLATE-CODON EXPECT WS-PROTEIN = SPACES