Property:More notes

From OLPC

Jump to: navigation, search

This is a property of type Text. (Type:Text is for strings that can be very long; you can't query for this value, but you can display it.)

Template:Test case, filled in by Form:Test case, adds this property to pages.

Here is a list of every page with Property:More notes

More notes
RecentChangesLinked/Category:User el-4 none
RecentChangesLinked/Sugar-jhbuild none
Skierpage/shikiwiki.css none
Tests/Acquiring a developer key None.
Tests/Activity/Calculate/AlgebraAndConstantTest The following is the test suite for algebra and constant test:
inputs(invalid, int, double, constants), sign(+,-), algebra(x!,x^2,root(x))

Base on Pairwise, we count and build 9 test cases, and 1 test case by Myer's.

We check the constants(pi, e) and use it by putting them as input values. We just test three of algebra operations, which are x!, x^2, root(x).More tests are needed to cover the other functions of the algebra feature.
Tests/Activity/Calculate/BooleanAndLabelTest The following is the test sequence for testing boolean feature(And, Or, Equal, Not Equal) and creating label:
input1(true, false, number, invalid), input2(true, false, number, invalid),
boolean operators (AND(&), OR , EQUAL(=), NOT EQUAL(!=)),
label (valid labels, invalid, no labels)
Based on Pairwise, we use TConfig to count and produce 12 test cases. In addition, based on Myer's, we build 3 test cases for invalid inputs for the test suite.
Tests/Activity/Calculate/CosSinTest test has passed.
Tests/Activity/Calculate/CosTest test has passed.
Tests/Activity/Calculate/FourArithmeticOperationsTest The following is the case sequence to test the four arithmetic operations(addition, subtract, multiply, division ):
input1(pos, neg, 0, invalid(a-z)), input2(pos, neg, 0, invalid(a-z)) ,operations(+,-,*,/)
We build 12 test cases using pairwise method and 2 test cases using Myer's method.
Tests/Activity/Calculate/PlusTest The following is the case sequence to test the four arithmetic operations(addition, subtract, multiply, division ):
 input1 (pos, neg, 0, invalid(a-z)), input2 (pos, neg, 0, invalid(a-z)) ,operations(+,-,*,/)
We build 14 tests for this test case by pairwise.
Tests/Activity/Calculate/SinCosTest test has passed.
Tests/Activity/Calculate/SinTest test has passed.
Tests/Activity/Calculate/SquareTest test has passed.
Tests/Activity/Calculate/additionTest test has passed.
Tests/Activity/Calculate/clearTest test has passed.
Tests/Activity/Calculate/cubeTest test has passed.
Tests/Activity/Calculate/divisionTest test has passed.
Tests/Activity/Calculate/logTest test has passed.
Tests/Activity/Calculate/multiplicationTest test has passed.
Tests/Activity/Calculate/squarerootTest test has passed.
Tests/Activity/Calculate/subtractionTest test has passed.
Tests/Activity/Calculate/tanTest test has passed.
Tests/Activity/Calculate/turnoffTest test has passed.
Tests/Activity/Calculate/turnon Test test has passed.
Tests/Activity/CalculateTests test has passed.
The following is the case sequence to test the four arithmetic operations(addition, subtract, multiply, division ):
 input1 (pos, neg, 0, invalid(a-z)), input2 (pos, neg, 0, invalid(a-z)) ,operations(+,-,*,/)

We build 14 tests for this test case by pairwise.
The following is the test suite for algebra and constant test:

inputs(invalid, int, double, constants), sign(+,-), algebra(x!,x^2,root(x))

Base on Pairwise, we count and build 9 test cases, and 1 test case by Myer's. We check the constants(pi, e) and use it by putting them as input values. We just test three of algebra operations, which are x!, x^2, root(x).More tests are needed to cover the other functions of the algebra feature.
The following is the test sequence for testing boolean feature(And, Or, Equal, Not Equal) and creating label:

input1(true, false, number, invalid), input2(true, false, number, invalid),
boolean operators (AND(&), OR , EQUAL(=), NOT EQUAL(!=)),
label (valid labels, invalid, no labels)

Based on Pairwise, we use TConfig to count and produce 12 test cases. In addition, based on Myer's, we build 3 test cases for invalid inputs for the test suite.
The following is the case sequence to test the four arithmetic operations(addition, subtract, multiply, division ):

input1(pos, neg, 0, invalid(a-z)), input2(pos, neg, 0, invalid(a-z)) ,operations(+,-,*,/)
We build 12 test cases using pairwise method and 2 test cases using Myer's method.
Tests/Activity/Chat None.
Tests/Activity/Chat/Private chat None.
Tests/Activity/Chat/Public chat None.
Tests/Activity/Clock * Only English, French and Spanish localizations are avalable at the present time.
Tests/Activity/Generic/Sanity Check Should be run on all XO platforms supported for a build, unless otherwise instructed.
Tests/Activity/Kuku/GameStartTest Game started successfully
Tests/Activity/Memorize This test is not applicable for the game when in sound mode
When user clicks on the boxes whoes revealed value dont match the system should identify it as not matching pair and re-conceal both the boxes.
The test is designed to check if the relevant value is displayed when we click on box.
Tests/Activity/Memorize/Non-matchingPair When user clicks on the boxes whoes revealed value dont match the system should identify it as not matching pair and re-conceal both the boxes.
Tests/Activity/Memorize/Reveal box The test is designed to check if the relevant value is displayed when we click on box.
Tests/Activity/Memorize/SameSideTesting This test is not applicable for the game when in sound mode
Tests/Activity/Paint See reported bugs
Tests/Activity/Read/Private sharing Stub test case.
Tests/Activity/Read/Public sharing Stub test case.
Tests/Activity/Record/Private photo sharing None
Tests/Activity/Record/Public photo sharing None.
Tests/Activity/TurtleArt Rationale:
  • Since these functions take two boolean inputs, it is feasable to test all possible combinations.
  • A pairwise approach is used to test the 'NOT' operator at the same time: All inputs to 'NOT' are tested while testing the outer logic operators without duplication.
    Assumptions:
  • All outputs are truncated to 1 decimal place.
  • Mathematically invalid operations should show a #syntaxerror
  • Arithmetic overflow is not likely to be a problem for the range of values required, hence is not tested.

Rationale

  • Moving the turtle and then checking its Y co-ordinate is used rather than directly checking the output from the math function is done because the print function itself seems to catch errors and write '0' regardless, whereas moving the turtle reveals these errors. Furthermore, moving the turtle again after the test indicates that the program is left in a working state.
  • Equivalence partitioning is used since the math functions take at most 2 inputs, and the number tests required to provide sufficient coverage is optimal.
  • Addition, Subtraction, Multiplication, Division & Modulo: Values are chosen from the partition class {Negative Real Number, 0.0, Positive Real Number}
  • Square Root: Values tested include {-1 (invalid), 0, 1, 4 (integer result), 7 (irrational result)}. These values were selected using Boundary Analysis.
    Rationale:
  • The equivalence partitions for the 'forward' and 'back' blocks are {Negative Number, Positive Number, Large Positive Number}
  • The equivalence partitions for the 'left' and 'right' blocks are {Negative Number, Positive Number < 360, Positive Number > 360}
  • It is assumed that the blocks function independently, so a member from each partition is tried once against each block.
  • This test sequence itself follows a simple use case: the user wants to draw a box with a dome on top.
    Rationale:
  • The inputs are chosen from the equivalence partition { Negative, Zero, Positive }
  • Input combinations were chosen to give a variety of outputs, for each partition. Boundary values are also tested.
Tests/Activity/TurtleArt Arithmetic Assumptions:
  • All outputs are truncated to 1 decimal place.
  • Mathematically invalid operations should show a #syntaxerror
  • Arithmetic overflow is not likely to be a problem for the range of values required, hence is not tested.

Rationale

  • Moving the turtle and then checking its Y co-ordinate is used rather than directly checking the output from the math function is done because the print function itself seems to catch errors and write '0' regardless, whereas moving the turtle reveals these errors. Furthermore, moving the turtle again after the test indicates that the program is left in a working state.
  • Equivalence partitioning is used since the math functions take at most 2 inputs, and the number tests required to provide sufficient coverage is optimal.
  • Addition, Subtraction, Multiplication, Division & Modulo: Values are chosen from the partition class {Negative Real Number, 0.0, Positive Real Number}
  • Square Root: Values tested include {-1 (invalid), 0, 1, 4 (integer result), 7 (irrational result)}. These values were selected using Boundary Analysis.
Tests/Activity/TurtleArt Boolean Logic 1 Rationale:
  • The inputs are chosen from the equivalence partition { Negative, Zero, Positive }
  • Input combinations were chosen to give a variety of outputs, for each partition. Boundary values are also tested.
Tests/Activity/TurtleArt Boolean Logic 2 Rationale:
  • Since these functions take two boolean inputs, it is feasable to test all possible combinations.
  • A pairwise approach is used to test the 'NOT' operator at the same time: All inputs to 'NOT' are tested while testing the outer logic operators without duplication.
Tests/Activity/TurtleArt Movement Rationale:
  • The equivalence partitions for the 'forward' and 'back' blocks are {Negative Number, Positive Number, Large Positive Number}
  • The equivalence partitions for the 'left' and 'right' blocks are {Negative Number, Positive Number < 360, Positive Number > 360}
  • It is assumed that the blocks function independently, so a member from each partition is tried once against each block.
  • This test sequence itself follows a simple use case: the user wants to draw a box with a dome on top.
Tests/Activity/Write/Private sharing Before starting the test, make sure that all participating laptops are seen in the Neighborhood view of each laptop!
Tests/Activity/x2o Pretty straight forward
Tests/Boot/Cleaninstall none
Tests/Boot/Security-Disabled none
Tests/Browse/Sharing bookmarks None.
… further results
Facts about More notesRDF feed
Has typeThis property is a special property in this wiki.TextThis type is among the standard datatypes of this wiki.

Pages using the property "More notes"

Showing 0 pages using this property.

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox