Testcase Query Examples
From OLPC
Other ways to query for test cases than the query(s) on Test cases 8.2.0
Copy these to make your own.
[edit] Basics
The basic query is
{{#ask: [[Category:Test cases]] [[Build stream::joyride|Any]] | additional options }}
One option you should always add is |default=Query for xyz found nothing?!, otherwise you'll have no indication a page has a query that isn't working.
See Inline query output formats.
[edit] Query counting each test case
There are 173 total test cases in Category:Test cases.
There are 27 test cases in Category:Test cases with Property:Build stream of Joyride.
There are 121 test cases in Category:Test cases with Property:Build stream of 8.2.
There are 93 test cases in Category:Test cases with category Activity.
[edit] Querying for test results (problematic!)
This is tricky, because multipled test results are lumped into one test case page. See Semantic MediaWiki#Issues for test results.
Show any test case for 8.2.1 with a bug number or a fail but the failure may not be in 8.2.1 testing.
| Short name | Build stream | PassFail | Trac bug number | Comments | |
|---|---|---|---|---|---|
| Tests/Activity/Memorize | Memorize Activity Same side testing FullFunctionTests Extra clicks Game finish Non-matching pair Value retention Game Start Reveal box Matching pair |
Any 8.2 8.2.1 |
Pass Fail |
memorize-27; successfully shared between two laptops on an AP. Still no win condition. Memorize icon appears in activity donut and pulses during startup Memorize activity opens properly Memorize activity closes properly Memorize icon disappears from the activity donut when activity closed Journal entry for previous activity session appears Clicking on Memorize journal entry restores activity to an appropriate state. FAIL because any pairs the player had revealed are lost and the user must start playing from scratch again. Addition opens properly Letters opens properly Sounds opens properly 4x4 produces the correct grid 5x5 produces the correct grid 6x6 produces the correct grid 4x4 grid allows only valid squares to highlight and be chosen for the 1st part of a turn A new random game is produced (using new game icon in top left corner) The ‘pair’ images disappear from the left when a new game is started Win with 4x4 grid playing addition Win with 5x5 grid playing letters Win with 6x6 grid playing Sounds Activity opens and creates new game, icon appears in Activity Doughnut Difficulty of (4x4) is selected and new games loads with 4x4 Load Demo of addition is selected and new game is created. When game of 4x4 addition is completed there is no sign or notification that the game has been completed, all the tiles are face up and highlighted purple but nothing else notifys the user that they were successful or that the game is over Activity is closed successfully and icon is removed from activity doughnut |
|
| Tests/Activity/Memorize/FullTest | FullFunctionTests | 8.2.1 | Pass Fail |
Activity opens and creates new game, icon appears in Activity Doughnut Difficulty of (4x4) is selected and new games loads with 4x4 Load Demo of addition is selected and new game is created. When game of 4x4 addition is completed there is no sign or notification that the game has been completed, all the tiles are face up and highlighted purple but nothing else notifys the user that they were successful or that the game is over Activity is closed successfully and icon is removed from activity doughnut |
|
| Tests/Activity/Memorize/FullTest3 | FullFunctionTest, Sequence 3 | 8.2.1 | Fail Pass |
Activity opens but previous games state is lost. Icon appears in Activity Doughnut When 6x6 is selected as the diffculty and the game type is selected as sounds a new game is loaded and displayed When 2 pieces are correctly matched they stay face up and gain a purple border. When game of 6x6 sounds is completed there is no sign or notification that the game has been completed, all the tiles are face up and highlighted purple but nothing else notifys the user that they were successful or that the game is over Activity is closed successfully and icon is removed from activity doughnut |
|
| Tests/Network/XO/WEP | WEP Access Point connection | 8.2 11.2 Any Joyride Staging 8.2.1 |
Pass | 92239,223 | no problems Started with cleaninstall of gg-766-3. started with cleaninstall It worked the second time I clicked on it and added the passphrase (ascii). Going back and forth between this and other APs, this one connects without asking for passphrase again and is pretty quick. used olpc-update on build 25 to candidate-800, and network via WEB works first reboot |
| Tests/SmokeTest/Activities | Activities | 8.2.1 11.2 Any 8.2 |
Fail Pass |
87388,738 | measure not working everything on track Signed clean-install of 766. olpc-update candidate-766 saw a bug where some older items were at the top of the journal queue despite not being worked in for quite some time. newer items were showing up below these. haven't reproduced yet. smoke testing firmware q2e21 Firmware q2e29a, software build os24.img |
[edit] Query displaying each test case
If the pages you are including are small, you can embed them with format=embedded. This is like transcluding each page with {{:Title of page}} {{:Another page}} ..., but dynamic. This can confuse editors, and it puts the page that uses it into any categories in the embedded pages!
The example below is limited to three results
Tests/Activity/Calculate/SquareTest
Obsolete, refer to [1].
Test case: square
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | Tests/Activity/Calculate/SquareTest | ||
| Objective | passed | ||
| Tools | calculater and numbers | ||
| Setup | |||
| Procedure | #turn on the calculator.
| ||
| Expected Results and Pass Criteria | number 4. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| 7.1.0 (650) | joyride | Pass |
|
Tests/Activity/CalculateTests
This Calculate Tests page is an amalgamation of test of the Calculate feature tests. Most of the tests date from 2009.
Calculate Activity Test
Test case: Calculate Activity
How to report results
| Stream | Any | ||
|---|---|---|---|
| Category | Activity | Sub-category | Calculate |
| Component | Calculate | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | basic activity testing | ||
| Tools | n/a | ||
| Setup | n/a | ||
| Procedure | # Activity installs from download (if not part of default installation) from website or USB key
| ||
| Expected Results and Pass Criteria | |||
| Comments | |||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Candidate | 8.2 | 760 | Pass | calculate-24 |
|
Calculate CosSin Test
Test case: cossin
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. type cos(sin(1)). 3. click on = button. | ||
| Expected Results and Pass Criteria | number 0.6663 | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Plus Test
Test case: FourArithmeticOperationsTest
How to report results
| Stream | 8.2 | ||
|---|---|---|---|
| Category | Activity | Sub-category | Calculate |
| Component | Calculate | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | |||
| Tools | n/a | ||
| Setup | n/a | ||
| Procedure | 1. Run the Calculate Activity on XO machine
2. Test invalid inputs for the fours arithmetic operations 3. Test valid inputs for the fours arithmetic operations | ||
| Expected Results and Pass Criteria | 1. When test the invalid inputs,like letters, the calculation should do not work out.
2. When test the valid inputs, the calculation should work out well, except any number divided by 0 (any number / 0), since it should be undefined for division. | ||
| Comments | 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. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Candidate | 8.2 | 2 | Pass | TestInvalidInputs:
When we test by inputing the invalid variables, we expect that the calculation should not do. For example, when input1 is a, and input2 is 1, then the calculation should do not work out for a + 1. The invalid inputs values are from a to Z. | 2009/03/26
| |
| Candidate | 8.2 | 12 | Pass | TestValidInputs:
The valid inputs values are numbers, and truth values(true and false). However, we just test the numbers as the inputs for the test case. We need do more tests to verity truth values for the fours arithmetic operations. | 2009/03/26
|
Calculate Square Test
Test case: square
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | Tests/Activity/Calculate/SquareTest | ||
| Objective | passed | ||
| Tools | calculater and numbers | ||
| Setup | |||
| Procedure | #turn on the calculator.
| ||
| Expected Results and Pass Criteria | number 4. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| 7.1.0 (650) | joyride | Pass |
|
Calculate Clear Test
Test case: clear
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on any number. 3. click on clear button. | ||
| Expected Results and Pass Criteria | screen is clear. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Log Test
Test case: log
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on 2 button. 3. click on log button. 4. click on = button. | ||
| Expected Results and Pass Criteria | number 0.3010 | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Subtraction Tests
Test case: subtraction
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on number 5. 3. click on - button. 4. click on number 2. 5. click on = button. | ||
| Expected Results and Pass Criteria | number 2. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Turn On Test
Test case: turnon
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. click on the calculator icon on the desktop of OLPC laptop.
2. check whether application is opening or not. 3. type some numbers on the screen. | ||
| Expected Results and Pass Criteria | calculator screen is open. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Tan Test
Test case: tan
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on number 1. 3. click on tan button. 4. click on = button. | ||
| Expected Results and Pass Criteria | number 1.5574 | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Multiplication Test
Test case: multiplication
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on 2 button. 3. click on * button. 4. click on 3 button. 5. click on = button. | ||
| Expected Results and Pass Criteria | number 6. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Cube Test
Test case: cube
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on 2 button. 3. click on x^3 button. 4. click on = button. | ||
| Expected Results and Pass Criteria | number 8. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Addition Test
Test case: addition
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | addition |
| Component | calculator and numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | addition of numbers | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on 1 button. 3. click on + button. 4. click on 2 button. 5. click on = button | ||
| Expected Results and Pass Criteria | number 3. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate SinCos Test
Test case: sincos
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. type sin(cos(1)). 3. click on = button or ans button. | ||
| Expected Results and Pass Criteria | number 0.5143. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Cos Test
Test case: cos
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator an dnumbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on number 2. 3. click on cos button. 4. click on = button. | ||
| Expected Results and Pass Criteria | number 0.5403 | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Pass | alsdfjasjsadlfksaflsdfkaslfdds |
|
Calculate Algebra and Constant Test
Test case: AlgebraAndConstantTest
How to report results
| Stream | 8.2 | ||
|---|---|---|---|
| Category | Activity | Sub-category | Calculate |
| Component | Calculate | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | Test three functions for the algebra feature, also test the constants of the Calculate activity | ||
| Tools | n/a | ||
| Setup | n/a | ||
| Procedure | 1. Open the XO machine
2. Run the Calculate Activity on XO machine 3. Test invalid inputs for algebra operation 4. Test valid inputs for algebra operation. Constants are checked and used as valid inputs. | ||
| Expected Results and Pass Criteria | When using invalid inputs like letters, it is expected that the tests to fail by informing the user with an error message.
When using valid inputs, it is expected that the tests will pass by returning the correct values. | ||
| Comments | 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. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Candidate | 8.2 | 1 | Pass | TestInvalidInputs:
We can not input letters(a-Z) to do algebra operation. | 2009/03/26
| |
| Candidate | 8.2 | 9 | Pass | TestValidInputs:
When the input number is negative, root(x) of algebra operation produce error as expected. When a double input is used for x!, the result is zero. | 2009/03/26
|
Boolean and Label Test
Test case: BooleanAndLabelTest
How to report results
| Stream | 8.2 | ||
|---|---|---|---|
| Category | Activity | Sub-category | Calculate |
| Component | Calculate | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | Test the boolean and the label features for the Calculate activity | ||
| Tools | n/a | ||
| Setup | n/a | ||
| 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 | When testing invalid inputs, it was expected that tests will fail by informing the user by an error message.
When testing valid inputs, it was expected that tests will pass returning the correct values. | ||
| 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(!=)), 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. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Candidate | 8.2 | 3 | Pass | 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 labels by these invalid values, but once you call these labels, then we can not get the value of these labels 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.However, We have not done any test for calling invalid label in this test suite. Therefore, more tests are needed. | 2009/03/26
| |
| Candidate | 8.2 | 12 | Pass | TestValidInputs:
The valid inputs for boolean feature are numbers(0,1,2,...) and truth value(true, false). The valid inputs for label name are letters or combination of letters and numbers. | 2009/03/26
|
Calculate Four Arithmetic Operations Tests
Test case: FourArithmeticOperationsTest
How to report results
| Stream | 8.2 | ||
|---|---|---|---|
| Category | Activity | Sub-category | Calculate |
| Component | Calculate | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | Test the calculate activity basic functionalities | ||
| Tools | n/a | ||
| Setup | n/a | ||
| Procedure | 1. Open the XO machine.
2. Run the Calculate Activity on XO machine. 3. Test invalid inputs for the four arithmetic operations. 4. Test valid inputs for the four arithmetic operations. | ||
| Expected Results and Pass Criteria | 1. When testing the invalid inputs, it is expected that tests will fail by returning some error message telling the user what went wrong.
2. When testing the valid inputs, it is expected that tests will pass by returning the right value. | ||
| Comments | 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. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Candidate | 8.2 | 2 | Pass | TestInvalidInputs:
When we test by inputting the invalid variables, we expect that the calculation should not work. For example, when input1 is a, and input2 is 1, then the calculation should not work out for a + 1. The invalid inputs values are from a to z. | 2009/03/26
| |
| Candidate | 8.2 | 12 | Pass | TestValidInputs:
The valid inputs values are numbers, and truth values(true and false). However, we just tested numbers as the inputs for the test cases. We do need more tests to verity truth values for the four arithmetic operations. | 2009/03/26
|
Calculate Sin Test
Test case: sin
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on number 1. 3. click on sin button. 4.click on = button. | ||
| Expected Results and Pass Criteria | number 0.8414 | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Division Test
Test case: division
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on 6 button. 3. click on / button. 4. click on 2 button. 5. click on = button. | ||
| Expected Results and Pass Criteria | number 3. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
== Calculate Square Root Test ==
Test case: squareroot
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculater and numbers | ||
| Setup | |||
| Procedure | 1. turn on the calculator.
2. click on number 1. 3. click on number 6. 4. click on square root button. 5. click on = button. | ||
| Expected Results and Pass Criteria | number 4. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Calculate Turn Off Test
Test case: turnoff
How to report results
| Stream | |||
|---|---|---|---|
| Category | Activity | Sub-category | calculate |
| Component | numbers | ||
| Feature | http://wiki.laptop.org/go/Calculate | ||
| Objective | passed | ||
| Tools | calculator and numbers | ||
| Setup | |||
| Procedure | 1. click on the exit button of the calculator application.
2. check whether the application is off or not. | ||
| Expected Results and Pass Criteria | application is off. | ||
| Comments | test has passed. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|
Tests/Activity/Chat
This Chat Tests page is an amalgamation of test of the Chat feature tests. Most of the tests date from 2009
Public Chat Test
Test case: Public Chat
How to report results
| Stream | 8.2, 11.2 | ||
|---|---|---|---|
| Category | Activity | Sub-category | Chat |
| Component | Chat | ||
| Feature | Chat | ||
| Objective | Verify that users can start and participate in a public (visible to the neighborhood) chat. | ||
| Tools | No test tools required. | ||
| Setup | At least two laptops running the same version of Chat, preferably the most recent. | ||
| Procedure | 1. Start up a Chat activity on one XO. Share it with the Neighborhood.
2. On the other XOs, go to the Neighborhood view and join the chat. | ||
| Expected Results and Pass Criteria | 1. When the XOs join the chat, the icon should appear with the colors of the host XO.
2. XOs can join the activity and chat reliably. | ||
| Comments | None. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Candidate | joyride | 2311 | Pass | No unexpected behavior. |
| |
| Candidate | 8.2 | 763 | Pass | chat-47 |
|
Private Chat Tests
Test case: Private Chat
How to report results
| Stream | 8.2, 11.2 | ||
|---|---|---|---|
| Category | Activity | Sub-category | Chat |
| Component | Chat | ||
| Feature | Chat | ||
| Objective | Verify that users can start and participate in a private (invite-only) chat. | ||
| Tools | No test tools required. | ||
| Setup | At least two laptops running the same version of Chat, preferably the most recent. | ||
| Procedure | 1. On one XO, start up the Chat activity.
2. Switch to the Neighborhood view.
5. Select the "join" option or click on the icon to join the chat. | ||
| Expected Results and Pass Criteria | 1. On the Neighborhood view, there should be no Chat icon representing the host visible anywhere.
2. XOs can join the activity and chat reliably. | ||
| Comments | None. | ||
| Release | Stream | Build | Pass/Fail | Trac Ticket(s) | Comment(s) | Date of Test |
|---|---|---|---|---|---|---|
| Candidate | joyride | 2311 | Pass | No unexpected behavior. |
|
[edit] Bug: query for a disallowed value sometimes still works
Bug: if I query for a bogus value, it counts all of them. A query for Build stream==BADVALUE returns a count of 147

