Testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 7: Line 7:
* [[Test meeting Minutes]] - Weekly meetings of interested test people, Mondays 1pm EDT
* [[Test meeting Minutes]] - Weekly meetings of interested test people, Mondays 1pm EDT
* [[Requirements]]
* [[Requirements]]
* [[Schoolserver Testing]]
* [http://www.laptop.org/en/jobs.shtml#QA%20Engineer QA engineer needed] - want to work at our office in Boston to coordinate testing? Apply now.
* [http://www.laptop.org/en/jobs.shtml#QA%20Engineer QA engineer needed] - want to work at our office in Boston to coordinate testing? Apply now.


Line 15: Line 14:


== Links of Interest ==
== Links of Interest ==
* [[Networking_scenarios]]
* [[Simple mesh test (Cerebro)]]
* [[Simple mesh test (Cerebro)]]
* [[Schoolserver Testing]]
* [[Test Group Release Notes]] - Quick info/smoke test on the latest builds. Read this before you bother to load a build
* [[Test Group Release Notes]] - Quick info/smoke test on the latest builds. Read this before you bother to load a build
** [[Update.1]] - test process for the Update.1 builds (691, 693, 697, &c)
** [[Update.1]] - test process for the Update.1 builds (691, 693, 697, &c)

Revision as of 17:53, 14 May 2008

  This page is monitored by the OLPC team.

The community and core team work through a slate of test issues for each major build and release. This page highlights the current tests being run, the testing process in general, and how to contribute your own results or bugs.

For the latest tests, see Update.1.

Notes and minutes

Older notes


Links of Interest

Equipment specs:

  • Infrastructure_AP: Zoom 4400 AP+2 Wireless-G Access Point (Approx. $50 USD)
  • Long range Wireless: Wavion’s WS410 Spatially Adaptive Wi-Fi Access Point (Approx. $1600 USD)
  • Server HW Specs (Approx. $3000 USD)


Check out these new links to test plans and result matrices -- Get involved and help test some activities:

Testing teams

The Activities on the XO have been developed by community members. Many of them are not well documented and there may not be much information on how to use them; so this testing can be described as 'Descriptive Testing', where you are helping to provide and/or correct the wiki pages that describe how an activity works. If you want to help, please refer to the Community Testing page for more details.

Testing at OLPC

Test Plans

To report results from a set of test cases, add a line to the appropriate table in the test case pages below with a quick summary; and include details, including setup and test team, on the talk page.

  • Update.1 test cases
  • Ship2.2 test cases - complete
  • User-focused test plans:
    User-focused test plans are being developed for all the basic features of the laptop, for many of the activities, and for the interaction with the school server, collaboration, connectivity, etc. Please follow the User-Focused Test Plans page to read, review, and help create test plans.

Items to Test

Areas that we need to test in house (due to the use of special equipment and quantities of laptops) include:

  • All keyboards. - Test: Keyboard Settings
    • Keys match the layouts designed
    • Language, keyboard, keymappings match the settings
    • All language and keyboard settings are preserved across updates
  • Languages - Test: Language Settings
  • Firmware
    • WPA - Richardo/Michailis
    • WEP - Richardo/Michailis
    • Mesh - upgrade under loaded network - Scott
    • Suspend/resume - Wad - Test: Suspend/resume
  • Scaling/performance
    • Jabber server scaling - OLPC/Collabora
    • Link local presence (Salut) - OLPC/Collabora
    • Journal/datastore
  • Upgrades /backward compatibility
  • Security


Other Test plans:


Schedule:

Please see the official roadmap (from the trac main page) for schedule dates and features for each release.

Also See

GSOC08 OLPC Project Automated Testing