samples/apifest1/day2/inputandoperation/test/org/netbeans/apifest/boolcircuit/RealTest.java
1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/samples/apifest1/day2/inputandoperation/test/org/netbeans/apifest/boolcircuit/RealTest.java Sat Jun 14 09:52:45 2008 +0200
1.3 @@ -0,0 +1,191 @@
1.4 +/*
1.5 + * The contents of this file are subject to the terms of the Common Development
1.6 + * and Distribution License (the License). You may not use this file except in
1.7 + * compliance with the License.
1.8 + *
1.9 + * You can obtain a copy of the License at http://www.netbeans.org/cddl.html
1.10 + * or http://www.netbeans.org/cddl.txt.
1.11 + *
1.12 + * When distributing Covered Code, include this CDDL Header Notice in each file
1.13 + * and include the License file at http://www.netbeans.org/cddl.txt.
1.14 + * If applicable, add the following below the CDDL Header, with the fields
1.15 + * enclosed by brackets [] replaced by your own identifying information:
1.16 + * "Portions Copyrighted [year] [name of copyright owner]"
1.17 + *
1.18 + * The Original Software is NetBeans. The Initial Developer of the Original
1.19 + * Software is Sun Microsystems, Inc. Portions Copyright 1997-2006 Sun
1.20 + * Microsystems, Inc. All Rights Reserved.
1.21 + */
1.22 +
1.23 +package org.netbeans.apifest.boolcircuit;
1.24 +
1.25 +import java.security.CodeSource;
1.26 +import java.security.Permission;
1.27 +import java.security.PermissionCollection;
1.28 +import java.security.Policy;
1.29 +import java.util.Collection;
1.30 +import java.util.Collections;
1.31 +import java.util.Enumeration;
1.32 +import junit.framework.TestCase;
1.33 +import junit.framework.*;
1.34 +
1.35 +/** This file contains the APIFest quest for day 2. Simply, turn the
1.36 + * boolean circuit into circuit that can compute with double values from 0 to 1.
1.37 + * <p>
1.38 + * This means that where ever a boolean was used to represent input or
1.39 + * output values, one can now use any double number from >= 0 and <= 1.
1.40 + * Still, to support backward compatibility, the operations with booleans
1.41 + * has to be kept available and have to work. In fact False shall be
1.42 + * treated as 0 and True as 1.
1.43 + * <p>
1.44 + * The basic elements has to be modified to work on doubles in the following
1.45 + * way:
1.46 + * <ul>
1.47 + * <li>negation - neg(x) = 1 - x, this is correct extension as neg(false)=neg(0)=1-0=1=true
1.48 + * <li>and - and(x,y) = x * y, again this is fine as and(true,true)=1*1=true and also
1.49 + * and(false,true)=0*1=0=false
1.50 + * <li>or - or(x,y) = 1 - (1 - x) * (1 - y) and this is also ok as
1.51 + * or(false,false) = 1 - (1 - 0) * (1 - 0) = 1 - 1 = 0 = false
1.52 + * or(true,false) = 1 - (1 - 1) * (1 - 0) = 1 - 0 * 1 = 1 = true
1.53 + * </ul>
1.54 + * <p>
1.55 + * However as the circuits with doubles are more rich than plain boolean circuits,
1.56 + * there is additional requirement to allow any user of your API to write its
1.57 + * own "element" type. This is all going to be exercise in the tests bellow
1.58 + * which you are supposed to implement.
1.59 + */
1.60 +public class RealTest extends TestCase {
1.61 + static {
1.62 + // your code shall run without any permissions
1.63 + }
1.64 +
1.65 + public RealTest(String testName) {
1.66 + super(testName);
1.67 + }
1.68 +
1.69 + protected void setUp() throws Exception {
1.70 + }
1.71 +
1.72 + protected void tearDown() throws Exception {
1.73 + }
1.74 +
1.75 +
1.76 + /** First of all create a circuit which will evaluate
1.77 + * expression (X1 and X2) or not(x1). Hold the circuit
1.78 + * in some variable.
1.79 + *
1.80 + * Feed this circuit with x1=true, x2=false, assert result is false
1.81 + *
1.82 + * Feed the same circuit with x1=false, x2=true, assert result is true
1.83 + *
1.84 + * Feed the same circuit with x1=0.0, x2=1.0, assert result is 1.0
1.85 + *
1.86 + * Feed the same circuit with x1=0.5, x2=0.5, assert result is 0.625
1.87 + *
1.88 + * Feed the same circuit with x1=0.0, x2=2.0, make sure it throws an exception
1.89 + */
1.90 + public void testX1andX2orNotX1() {
1.91 + VariableInput x1 = Factory.createVariableInput();
1.92 + VariableInput x2 = Factory.createVariableInput();
1.93 + Operation and = Factory.createAndOperation(x1, x2);
1.94 + Operation not = Factory.createNotOperation(x1);
1.95 + Operation or = Factory.createOrOperation(Factory.createOperationBasedInput(and), Factory.createOperationBasedInput(not));
1.96 +
1.97 + x1.setBooleanValue(false);
1.98 + x2.setBooleanValue(true);
1.99 + assertTrue(Circuit.evaluateBooleanOperation(or));
1.100 +
1.101 + x1.setRealValue(0.0);
1.102 + x2.setRealValue(1.0);
1.103 + assertEquals(1.0, Circuit.evaluateRealOperation(or));
1.104 +
1.105 + x1.setRealValue(0.5);
1.106 + x2.setRealValue(0.5);
1.107 + assertEquals(0.625, Circuit.evaluateRealOperation(or));
1.108 +
1.109 + try {
1.110 + x1.setRealValue(0.0);
1.111 + x2.setRealValue(2.0);
1.112 + Circuit.evaluateRealOperation(or);
1.113 + fail();
1.114 + } catch (IllegalArgumentException exc) {
1.115 + //good..
1.116 + }
1.117 +
1.118 + }
1.119 +
1.120 + /** Ensure that one variable cannot be filled with two different values.
1.121 + * Create a circuit for x1 and x1. Make sure that for any usage of your
1.122 + * API that would not lead to x1 * x1 result, an exception is thrown.
1.123 + * For example if there was a way to feed the circuit with two different
1.124 + * values 0.3 and 0.5 an exception is thrown indicating that this is
1.125 + * improper use of the circuit.
1.126 + */
1.127 + public void testImproperUseOfTheCircuit() {
1.128 +
1.129 + // this is enforced by the setter on the VariableInput.. how to test??
1.130 +
1.131 +
1.132 +
1.133 +// fail("task2");
1.134 + // PS: This request is based on observation that some API from day1
1.135 + // solved the multiple usage of one variable, by repeating its
1.136 + // value multiple times. This tasks says that if this is case of
1.137 + // your API you must make sure, when that usage of different values
1.138 + // for one variable is prohibited. If there is no way in your API to
1.139 + // express this task, just say so, and you do not need to write a test.
1.140 + // However if anyone else finds a way to simulate such situation in your
1.141 + // API later, it will get points for breaking your API.
1.142 + }
1.143 +
1.144 + /** Write your own element type called "gte" that will have two inputs and one output.
1.145 + * The output value will be 1 if x1 >= x2 and 0 otherwise.
1.146 + *
1.147 + * Create
1.148 + * circuit for following expression: (x1 and not(x1)) gte x1
1.149 + *
1.150 + * Feed the circuit with 0.5 and verify the result is 0
1.151 + *
1.152 + * Feed the same circuit with 1 and verify the result is 0
1.153 + *
1.154 + * Feed the same circuit with 0 and verify the result is 1
1.155 + */
1.156 + public void testGreaterThanEqualElement() {
1.157 + VariableInput x1 = Factory.createVariableInput();
1.158 + Operation not = Factory.createNotOperation(x1);
1.159 + Operation and = Factory.createAndOperation(x1, Factory.createOperationBasedInput(not));
1.160 + Operation gte = new GTEOperation(Factory.createOperationBasedInput(and), x1);
1.161 +
1.162 + x1.setRealValue(0.5);
1.163 + assertEquals(0.0, Circuit.evaluateRealOperation(gte));
1.164 +
1.165 + x1.setRealValue(1.0);
1.166 + assertEquals(0.0, Circuit.evaluateRealOperation(gte));
1.167 +
1.168 + x1.setRealValue(0.0);
1.169 + assertEquals(1.0, Circuit.evaluateRealOperation(gte));
1.170 +
1.171 + }
1.172 +
1.173 + private final class GTEOperation extends Operation {
1.174 +
1.175 + private Input input2;
1.176 +
1.177 + private Input input1;
1.178 +
1.179 + public GTEOperation(Input in1, Input in2) {
1.180 + super();
1.181 + input1 = in1;
1.182 + input2 = in2;
1.183 + }
1.184 +
1.185 + public boolean performBooleanOperation() {
1.186 + return input1.getRealValue() >= input2.getRealValue();
1.187 + }
1.188 +
1.189 + public double performRealOperation() {
1.190 + return (input1.getRealValue() >= input2.getRealValue()) ? 1.0 : 0.0;
1.191 + }
1.192 +
1.193 + }
1.194 +}