Tests/Activity/Calculate/BooleanAndLabelTest: Difference between revisions
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
|testcase_expectedresults=When we test invalid inputs, we hope the calculate activity should produce error. When we test valid inputs, we hope that the activity do well. |
|testcase_expectedresults=When we test invalid inputs, we hope the calculate activity should produce error. When we test valid inputs, we hope that the activity do well. |
||
|testcase_comments=The following is the test sequence for testing boolean feature(And, Or, Equal, Not Equal) and creating label: |
|testcase_comments=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(!=)), |
boolean operators (AND(&), OR , EQUAL(=), NOT EQUAL(!=)), |
||
label (valid labels, invalid, no labels) |
label (valid labels, invalid, no labels) |
||
Based on Pairwise, we use TConfig to count and produce 12 test cases to do. In addition, based on Myer's, we build 3 test cases for invalid inputs for the test sequence. |
Based on Pairwise, we use TConfig to count and produce 12 test cases to do. In addition, based on Myer's, we build 3 test cases for invalid inputs for the test sequence. |
||
Revision as of 02:43, 26 March 2009
| Stream | ,|x|Build stream::x}} | ||
|---|---|---|---|
| Category | Test category::Activity | Sub-category | Test subcategory::Calculate |
| Component | System component::Calculate | ||
| Feature | System feature::http://wiki.laptop.org/go/Calculate | ||
| Objective | Test objective::Test the boolean feature and label of calculate activity doing well or not | ||
| Tools | Test tools::n/a | ||
| Setup | Test setup::n/a | ||
| Procedure | [[Test procedure::1. Open the XO machine
2. Run the calculate activity on XO machine 3. Test invalid inputs 4. Test valid inputs]] | ||
| Expected Results and Pass Criteria |
Pass criteria::When we test invalid inputs, we hope the calculate activity should produce error. When we test valid inputs, we hope that the activity do well. | ||
| Comments | [[More notes::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 to do. In addition, based on Myer's, we build 3 test cases for invalid inputs for the test sequence.]] | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Software release::Candidate | Build stream::8.2 | Build number::3 | PassFail::Pass | ,|x| #x}} | [[Comments::TestInvalidInputs:
The invalid inputs for boolean features are letters from a to Z. The invalid inputs for label name are only symbols(&,+,=,and so on), numbers(1,2,...), and truth value(true, false). We can name labells by these invalid values, but once you call these labells, then you can not get the value of these labells stand for. The calculation still work out, but the result is not right as you expect to get. We think here is a bug for label. We have not do any test on calling label in this test sequence. There are more tests to be needed for it.]] |
Created::2009/03/26
|
| Software release::Candidate | Build stream::8.2 | Build number::12 | PassFail::Pass | ,|x| #x}} | [[Comments::TestValidInputs:
The valid inputs for boolean feature are numbers(1,2,...) and truth value(true, false). The valid inputs for label name are letters or combination of letters and numbers.]] |
Created::2009/03/26
|