Problem 44631. Make your own Test Suite (part 0)

Created by David Verrelli

Solve Later

{"relationships":[{"relationshipType":"http://schemas.mathworks.com/matlab/code/2013/relationships/document","targetMode":"","relationshipId":"rId1","target":"/matlab/document.xml"},{"relationshipType":"http://schemas.mathworks.com/matlab/code/2013/relationships/output","targetMode":"","relationshipId":"rId2","target":"/matlab/output.xml"}],"parts":[{"partUri":"/matlab/document.xml","relationship":[],"contentType":"application/vnd.mathworks.matlab.code.document+xml","content":"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<w:document xmlns:w=\"http://schemas.openxmlformats.org/wordprocessingml/2006/main\"><w:body><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:rPr><w:i/></w:rPr><w:t>Have no knowledge of</w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t> </w:t></w:r><w:hyperlink w:docLocation=\"https://au.mathworks.com/help/matlab/matlab_prog/floating-point-numbers.html\"><w:r><w:rPr><w:i/></w:rPr><w:t>\"floating-point numbers\"</w:t></w:r></w:hyperlink><w:r><w:rPr><w:i/></w:rPr><w:t>? Read the documentation, and/or try</w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t> </w:t></w:r><w:hyperlink w:docLocation=\"https://www.mathworks.com/matlabcentral/cody/problems/44690\"><w:r><w:rPr><w:i/></w:rPr><w:t>Problem 44690</w:t></w:r></w:hyperlink><w:r><w:rPr><w:i/></w:rPr><w:t> first.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>——————————————————————————————————————————</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>In this task you need to imagine that you —</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>yes, YOU</w:t></w:r><w:r><w:t> — have developed a problem on Cody for</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>me</w:t></w:r><w:r><w:t> to solve, and now</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:b/></w:rPr><w:t>you need to draft a naïve Test Suite</w:t></w:r><w:r><w:t> as the first step in developing a more robust Test Suite that would check whether</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>my</w:t></w:r><w:r><w:t> submitted solutions meet</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>your</w:t></w:r><w:r><w:t> requirements or not.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>So the tables are turned! You are now in the role of Tester! I am in the role of Player!</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>The problem you've set me is to:</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"ListParagraph\"/><w:numPr><w:numId w:val=\"1\"/></w:numPr></w:pPr><w:r><w:t>output the</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:b/></w:rPr><w:t>sine</w:t></w:r><w:r><w:t> of an angle, when the angle is specified in degrees as a (scalar)</w:t></w:r><w:r><w:t> </w:t></w:r><w:hyperlink w:docLocation=\"https://au.mathworks.com/help/matlab/ref/double.html\"><w:r><w:rPr><w:rFonts w:cs=\"monospace\"/></w:rPr><w:t>double</w:t></w:r></w:hyperlink><w:r><w:t>, with no restriction in the domain.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>You provide me with the following example for the function defined as</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:rFonts w:cs=\"monospace\"/></w:rPr><w:t>s = SINE(a)</w:t></w:r><w:r><w:t>:</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"code\"/></w:pPr><w:r><w:t><![CDATA[ % INPUT\n a = 45 % degrees\n % OUTPUT\n s = 1/sqrt(2)]]></w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>Now I have responded by submitting a large number of purported 'solutions', some of which are</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>reasonably accurate</w:t></w:r><w:r><w:t>, and others which are either too imprecise or else logically flawed.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>Your final Test Suite (contained within</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>your</w:t></w:r><w:r><w:t> function</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:rFonts w:cs=\"monospace\"/></w:rPr><w:t>testSuite</w:t></w:r><w:r><w:t>) will have to address several aspects arising in your problem specification. However, for this 'first draft' you are creating a naïve Test Suite with only one requirement:</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"ListParagraph\"/><w:numPr><w:numId w:val=\"2\"/></w:numPr></w:pPr><w:r><w:t>Check that my submitted code reliably returns</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:b/></w:rPr><w:t>sufficiently accurate</w:t></w:r><w:r><w:t> values for sine of many different angles. Use the</w:t></w:r><w:r><w:t> </w:t></w:r><w:hyperlink w:docLocation=\"https://au.mathworks.com/help/matlab/ref/assert.html\"><w:r><w:rPr><w:rFonts w:cs=\"monospace\"/></w:rPr><w:t>assert</w:t></w:r></w:hyperlink><w:r><w:t> function to generate</w:t></w:r><w:r><w:t> </w:t></w:r><w:hyperlink w:docLocation=\"https://www.mathworks.com/matlabcentral/cody/problems/44357\"><w:r><w:t>errors/exceptions</w:t></w:r></w:hyperlink><w:r><w:t> if the values are not sufficiently accurate.</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>You</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:b/></w:rPr><w:t>can</w:t></w:r><w:r><w:t> use the functions</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:rFonts w:cs=\"monospace\"/></w:rPr><w:t>sind</w:t></w:r><w:r><w:t>,</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:rFonts w:cs=\"monospace\"/></w:rPr><w:t>sin</w:t></w:r><w:r><w:t>,</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>etc.</w:t></w:r><w:r><w:t> in this draft Test Suite, if you want — even though this would be bad practice in your final Test Suite!</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"text\"/></w:pPr><w:r><w:t>Thus, the above specification is merely a</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:i/></w:rPr><w:t>starting point</w:t></w:r><w:r><w:t>. You will develop more robust Test Suites in:</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"ListParagraph\"/><w:numPr><w:numId w:val=\"1\"/></w:numPr></w:pPr><w:hyperlink w:docLocation=\"https://www.mathworks.com/matlabcentral/cody/problems/44617\"><w:r><w:t>Problem 44617</w:t></w:r></w:hyperlink><w:r><w:t> (part</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:b/></w:rPr><w:t>1</w:t></w:r><w:r><w:t>)</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"ListParagraph\"/><w:numPr><w:numId w:val=\"1\"/></w:numPr></w:pPr><w:hyperlink w:docLocation=\"https://www.mathworks.com/matlabcentral/cody/problems/44616\"><w:r><w:t>Problem 44616</w:t></w:r></w:hyperlink><w:r><w:t> (part</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:b/></w:rPr><w:t>2</w:t></w:r><w:r><w:t>)</w:t></w:r></w:p><w:p><w:pPr><w:pStyle w:val=\"ListParagraph\"/><w:numPr><w:numId w:val=\"1\"/></w:numPr></w:pPr><w:hyperlink w:docLocation=\"https://www.mathworks.com/matlabcentral/cody/problems/44521\"><w:r><w:t>Problem 44521</w:t></w:r></w:hyperlink><w:r><w:t> (part</w:t></w:r><w:r><w:t> </w:t></w:r><w:r><w:rPr><w:b/></w:rPr><w:t>3</w:t></w:r><w:r><w:t>)</w:t></w:r></w:p></w:body></w:document>"},{"partUri":"/matlab/output.xml","contentType":"text/xml","content":"<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\" ?><embeddedOutputs><metaData><evaluationState>manual</evaluationState><layoutState>code</layoutState><outputStatus>ready</outputStatus></metaData><outputArray type=\"array\"/><regionArray type=\"array\"/></embeddedOutputs>"}]}

Have no knowledge of <a href = "https://au.mathworks.com/help/matlab/matlab_prog/floating-point-numbers.html">"floating-point numbers"</a>? Read the documentation, and/or try <a href = "https://www.mathworks.com/matlabcentral/cody/problems/44690">Problem 44690</a> first.——————————————————————————————————————————In this task you need to imagine that you — yes, YOU — have developed a problem on Cody for me to solve, and now you need to draft a naïve Test Suite as the first step in developing a more robust Test Suite that would check whether my submitted solutions meet your requirements or not.So the tables are turned! You are now in the role of Tester! I am in the role of Player!The problem you've set me is to:<ul><li>output the sine of an angle, when the angle is specified in degrees as a (scalar) <a href = "https://au.mathworks.com/help/matlab/ref/double.html"><tt>double</tt></a>, with no restriction in the domain.</li></ul>You provide me with the following example for the function defined as <tt>s = SINE(a)</tt>:<pre> % INPUT
 a = 45 % degrees
 % OUTPUT
 s = 1/sqrt(2)</pre>Now I have responded by submitting a large number of purported 'solutions', some of which are reasonably accurate, and others which are either too imprecise or else logically flawed.Your final Test Suite (contained within your function <tt>testSuite</tt>) will have to address several aspects arising in your problem specification. However, for this 'first draft' you are creating a naïve Test Suite with only one requirement:<ol><li>Check that my submitted code reliably returns sufficiently accurate values for sine of many different angles. Use the <a href = "https://au.mathworks.com/help/matlab/ref/assert.html"><tt>assert</tt></a> function to generate <a href = "https://www.mathworks.com/matlabcentral/cody/problems/44357">errors/exceptions</a> if the values are not sufficiently accurate.</li></ol>You can use the functions <tt>sind</tt>, <tt>sin</tt>, etc. in this draft Test Suite, if you want — even though this would be bad practice in your final Test Suite!Thus, the above specification is merely a starting point. You will develop more robust Test Suites in:<ul><li><a href = "https://www.mathworks.com/matlabcentral/cody/problems/44617">Problem 44617</a> (part 1)</li><li><a href = "https://www.mathworks.com/matlabcentral/cody/problems/44616">Problem 44616</a> (part 2)</li><li><a href = "https://www.mathworks.com/matlabcentral/cody/problems/44521">Problem 44521</a> (part 3)</li></ul>

_Have no knowledge of <https://au.mathworks.com/help/matlab/matlab_prog/floating-point-numbers.html "floating-point numbers">? Read the documentation, and/or try <https://www.mathworks.com/matlabcentral/cody/problems/44690 Problem 44690> first._

——————————————————————————————————————————

In this task you need to imagine that you — _yes, YOU_ — have developed a problem on Cody for _me_ to solve, and now *you need to draft a naïve Test Suite* as the first step in developing a more robust Test Suite that would check whether _my_ submitted solutions meet _your_ requirements or not.

So the tables are turned!  You are now in the role of Tester!  I am in the role of Player!

The problem you've set me is to:

* output the *sine* of an angle, when the angle is specified in degrees as a (scalar) <https://au.mathworks.com/help/matlab/ref/double.html |double|>, with no restriction in the domain.

You provide me with the following example for the function defined as |s = SINE(a)|:

% INPUT
 a = 45 % degrees
 % OUTPUT
 s = 1/sqrt(2)

Now I have responded by submitting a large number of purported 'solutions', some of which are _reasonably accurate_, and others which are either too imprecise or else logically flawed.

Your final Test Suite (contained within _your_ function |testSuite|) will have to address several aspects arising in your problem specification.  However, for this 'first draft' you are creating a naïve Test Suite with only one requirement:

# Check that my submitted code reliably returns *sufficiently accurate* values for sine of many different angles. Use the <https://au.mathworks.com/help/matlab/ref/assert.html |assert|> function to generate <https://www.mathworks.com/matlabcentral/cody/problems/44357 errors/exceptions> if the values are not sufficiently accurate.

You *can* use the functions |sind|, |sin|, _etc._ in this draft Test Suite, if you want — even though this would be bad practice in your final Test Suite!

Thus, the above specification is merely a _starting point_.  You will develop more robust Test Suites in:

* <https://www.mathworks.com/matlabcentral/cody/problems/44617 Problem 44617> (part *1*)
* <https://www.mathworks.com/matlabcentral/cody/problems/44616 Problem 44616> (part *2*)
* <https://www.mathworks.com/matlabcentral/cody/problems/44521 Problem 44521> (part *3*)

Solve

Solution Stats

64 Solutions
5 Solvers

Last Solution submitted on Aug 25, 2021

Last 200 Solutions

Problem Comments

6 Comments

6 Comments

Show 3 older comments

David Verrelli on 2 Jun 2018

Hint: when the Problem Statement uses phrases like "reasonably accurate" and "sufficiently accurate", it is a clue that your Test Suite should not require 'equality' to any 'exact values', but rather should include a small tolerance to allow for unavoidable floating-point imprecision.

Pavel on 9 Jun 2018

It was very hard to understand what do you mean.

David Verrelli on 10 Jun 2018

I'm glad you managed to find a solution. I tried to provide a few extra clues, such as in the Solution Template and in the comment from 02 June. Players will benefit from looking up the Documentation on functions such as "assert", "isequal", etc., along with information on "Floating-Point Numbers" at https://au.mathworks.com/help/matlab/matlab_prog/floating-point-numbers.html . There are also many other resources online, such as www.floating-point-gui.de . For some people this should be a simple problem to implement their existing knowledge; for other people, it should be a learning process. —DIV

Rafael S.T. Vieira on 12 Aug 2020

Since assert is not working anymore, it is necessary to use the dummy variable and the function error.

David Verrelli on 19 Jul 2021

Rafael, I had not been not aware that the assert() function has been disallowed on Cody. Thank-you for alerting us to that.
Previously it was working, and actually it is the function that ideally 'should' be used, so I am not going to alter the problem statement.

However I agree that with the current Cody prohibition on players using assert() in their solutions, the error() function will have to be used instead.
However, I can confirm that it is *not* necessary to use any dummy variables at all.

P.S. I believe assert() was disallowed because of a small number of Cody players who brazenly cheated their way through numerous problems. Ideally there should be a switch in Cody to allow the assert() function to be used for specific individual problems, in which case there are some special measures that can be implemented to prevent such exploits. For example, running the command "! rm -v assert.m" (without quotation marks) in the Test Suite.

goc3 on 3 Aug 2021

David, I agree 100% that certain functions should be allowed in individual problems, if selected by the problem author.

Problem Recent Solvers5

Problem Tags

assert cody basics finite precision floating-point numbers meta-problem test suite testing times

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!