samples/apifest1/day2/RealTest.java
author Jaroslav Tulach <jtulach@netbeans.org>
Sat, 14 Jun 2008 09:58:08 +0200
changeset 153 b5cbb797ec0a
parent 133 50bf1b976c0d
child 154 0fd5e9c500b9
permissions -rw-r--r--
up to line 2000
     1 /*
     2  * The contents of this file are subject to the terms of the Common Development
     3  * and Distribution License (the License). You may not use this file except in
     4  * compliance with the License.
     5  *
     6  * You can obtain a copy of the License at http://www.netbeans.org/cddl.html
     7  * or http://www.netbeans.org/cddl.txt.
     8  *
     9  * When distributing Covered Code, include this CDDL Header Notice in each file
    10  * and include the License file at http://www.netbeans.org/cddl.txt.
    11  * If applicable, add the following below the CDDL Header, with the fields
    12  * enclosed by brackets [] replaced by your own identifying information:
    13  * "Portions Copyrighted [year] [name of copyright owner]"
    14  *
    15  * The Original Software is NetBeans. The Initial Developer of the Original
    16  * Software is Sun Microsystems, Inc. Portions Copyright 1997-2006 Sun
    17  * Microsystems, Inc. All Rights Reserved.
    18  */
    19 
    20 package org.netbeans.apifest.boolcircuit;
    21 
    22 import java.security.CodeSource;
    23 import java.security.Permission;
    24 import java.security.PermissionCollection;
    25 import java.security.Policy;
    26 import java.util.Collection;
    27 import java.util.Collections;
    28 import java.util.Enumeration;
    29 import junit.framework.TestCase;
    30 import junit.framework.*;
    31 
    32 // BEGIN: apitest.day2.RealTest
    33 /** This file contains the APIFest quest for day 2. Simply, turn the 
    34  * boolean circuit into circuit that can compute with double values from 0 to 1.
    35  * <p>
    36  * This means that where ever a boolean was used to represent input or 
    37  * output values, one can now use any double number from >= 0 and <= 1.
    38  * Still, to support backward compatibility, the operations with booleans
    39  * has to be kept available and have to work. In fact False shall be 
    40  * treated as 0 and True as 1.
    41  * <p>
    42  * The basic elements has to be modified to work on doubles in the following
    43  * way:
    44  * <ul>
    45  *   <li>negation - neg(x) = 1 - x, this is correct extension as neg(false)=neg(0)=1-0=1=true
    46  *   <li>and - and(x,y) = x * y, again this is fine as and(true,true)=1*1=true and also
    47  *             and(false,true)=0*1=0=false
    48  *   <li>or - or(x,y) = 1 - (1 - x) * (1 - y) and this is also ok as
    49  *             or(false,false) = 1 - (1 - 0) * (1 - 0) = 1 - 1 = 0 = false
    50  *             or(true,false) = 1 - (1 - 1) * (1 - 0) = 1 - 0 * 1 = 1 = true
    51  * </ul>
    52  * <p>
    53  * However as the circuits with doubles are more rich than plain boolean circuits,
    54  * there is additional requirement to allow any user of your API to write its 
    55  * own "element" type. This is all going to be exercise in the tests bellow
    56  * which you are supposed to implement.
    57  */
    58 public class RealTest extends TestCase {
    59     static {
    60         // your code shall run without any permissions
    61     }
    62     
    63     public RealTest(String testName) {
    64         super(testName);
    65     }
    66 
    67     
    68     /** First of all create a circuit which will evaluate
    69      * expression (X1 and X2) or not(x1). Hold the circuit
    70      * in some variable.
    71      *
    72      * Feed this circuit with x1=true, x2=false, assert result is false
    73      *
    74      * Feed the same circuit with x1=false, x2=true, assert result is true
    75      *
    76      * Feed the same circuit with x1=0.0, x2=1.0, assert result is 1.0
    77      *
    78      * Feed the same circuit with x1=0.5, x2=0.5, assert result is 0.625
    79      *
    80      * Feed the same circuit with x1=0.0, x2=2.0, make sure it throws an exception
    81      */
    82     public void testX1andX2orNotX1() {
    83         fail("testX1andX2orNotX1");
    84     }
    85     
    86     /** Ensure that one variable cannot be filled with two different values.
    87      * Create a circuit for x1 and x1. Make sure that for any usage of your
    88      * API that would not lead to x1 * x1 result, an exception is thrown.
    89      * For example if there was a way to feed the circuit with two different 
    90      * values 0.3 and 0.5 an exception is thrown indicating that this is 
    91      * improper use of the circuit.
    92      */
    93     public void testImproperUseOfTheCircuit() {
    94         fail("testImproperUseOfTheCircuit");
    95     }
    96     
    97     /** Write your own element type called "gte" that will have two inputs and one output.
    98      * The output value will be 1 if x1 >= x2 and 0 otherwise. 
    99      * 
   100      * Create 
   101      * circuit for following expression: (x1 and not(x1)) gte x1
   102      *
   103      * Feed the circuit with 0.5 and verify the result is 0
   104      *
   105      * Feed the same circuit with 1 and verify the result is 0
   106      *
   107      * Feed the same circuit with 0 and verify the result is 1
   108      */
   109     public void testGreaterThanEqualElement() {
   110         fail("testGreaterThanEqualElement");
   111     }
   112 }
   113 // END: apitest.day2.RealTest
   114