Test Automation - CTI for TET - G11n Test Suite
Basic Information
- Project name: G11n Automated Testing
- Short description: The goal of this project is to provide g11n test suite using Common Test Infrastructure (CTI) framework and Test Environment Toolkit (TET)
- Responsible person(s) contact: petr.hruska@sun.com
Project Milestones:
- Phase 1 - create G11n basic test suite for OpenSolaris Binary Distro
- Phase 2 - create an extended/regression test suites for OpenSolaris Binary Distro
- Phase 3 - establish a project at OpenSolaris.org, create a mercurial repository there and place a test suites there
- Phase 4 - contribute some tests to testing community at OpenSolaris.org
| Date | Comments |
|---|---|
| 07/21/2009 | Phase 1 started, evaluation of existing tests |
| 08/13/2009 | Phase 1 review, basic test suite created, currently having 10+ tests |
How to Start
- download TETlite package
- install CTI for TET by standard Solaris package installation tool pkgadd (available also for OpenSolaris) with root privileges:
pkgadd -d {package location} SUNWstc-tetlite
- package is installed to /opt/SUNWstc-tetlite by default
Test Suite Execution
- the test suite execution is required to be done as root
- setup the environment variables:
export TET_ROOT=/opt/SUNWstc-tetlite export TET_SUITE_ROOT=path_to_test_suite export CTI_ROOT=/opt/SUNWstc-tetlite/contrib/ctitools export PATH=$PATH:/opt/SUNWstc-tetlite/contrib/ctitools/bin
- run script
# run_test TestSuiteName_ts scriptName
Test Suites
G11n Basic Test Suite
| Test ID | Status | Incl. to OpenSolaris Test Suite | Next Steps | Migrated/Created by | Style Review | Functionality Review | Putback Approval |
|---|---|---|---|---|---|---|---|
| logErrorCheck.ksh (OS001-logs,S004-logErrorCheck | ready | yes | copy install logs, warnings should not fail the test | Kristyna | READY | READY | |
| S001-init | ready | yes | Martin | need correction | |||
| S002-core_files | ready | yes | transform to g11n regression test | Kristyna | READY | need corrections? | |
| S003-pkgchk | in progress | yes | modify it for osol, create homepage | Martin | |||
| S005-bounCe | ready | yes | provide also full log | Martin | need corrections | need corrections? | |
| [S006-localedata ] | in progress | no | merge with S010 | Petko | |||
| S007-linkcheck | ready | yes | to be merged with S014 | Kristyna | READY | finished | |
| S008-lc_check | on hold | no | migration currently not planned | Slavek | |||
| S009-broken-links | ready | yes | create homepage, check against g11n packages, include full links in log | Martin | need corrections | need corrections | |
| S010-validate-locale | ready | yes | S006 to be added, create summary in log, analyze failed status | Petko | READY? | need corrections | |
| S011-locale-regression-check | completed | yes | create homepage | Petko | READY? | need corrections | |
| S012-binaryCat | ready | yes | sparc need to be check yet, missing results in report | Kristyna | READY | finished | |
| S013-mocheck | ready | yes | create list of supported apps | Slavek | need corrections | ||
| S014-l10n_msgtest | in progress | yes | merge with S007, create summary in log, evaluate if l10n mesg test is possible for firefox | Martin | |||
| S015-keyboards | ready | yes | create homepage, check error reporting | Petko | READY? | need corrections | |
| [S016-track_kb_changes ] | on hold | no | to be evaluated | Petko | |||
| S017-duplicate | ready | yes | check against g11n packages | Martin | need corrections | need corrections | |
| S018-svcs | on hold | no | evaluate services from g11n perspective | Slavek | |||
| S019-login-logout | ready | yes | create homepage, ensure session is started the same way as from gdm | Petko | need corrections | ||
| S020-sorting | ready | yes | add missing golden files, attach full log | Slavek | need corrections | ||
| S021-x_files | completed | yes | Kristyna | READY | finished | ||
| S022-locale_map | completed | yes | Martin | need corrections | |||
| correct_symlink | ready | yes | Martin | need corrections | need corrections |
NOTE: Review collumns should contain these descriptors:
need corrections - there are some issues that should be changed
in progress - meaning is obvious
recheck - corrections have been made and it is necessary to recheck current test (reviewer should recheck the test)
READY - the review was succesfull
Extended Test Suite
| Test ID | Status | Incl. to OpenSolaris Test Suite | Incl. to SXCE test suite | Migrated/Created by |
|---|---|---|---|---|
Links & Docs
- Jim Walker's presentation: http://opensolaris.org/os/community/testing/files/opensolaris_testing.pdf
- OpenSolaris Self-Service Testing project homepage: http://www.opensolaris.org/os/community/testing/selftest/
- Information on the OpenSolaris test farm is at: http://opensolaris.org/os/community/testing/testfarm
- OpenSolaris users can access the test farm at: http://test.opensolaris.org/testfarm
- Information on the test farm zone implementation is at: http://opensolaris.org/os/community/testing/testfarm/zones
- Test Suites: http://opensolaris.org/os/community/testing/testsuites/
- STF - Solaris Test Framework: http://opensolaris.org/os/community/testing/testsuites/stf/
- TET - Test Environment Toolkit: http://tetworks.opengroup.org/tet/
more documentation on: http://tetworks.opengroup.org/documents/docs37.htm- CTI for TET - Common Test Infrastructure for TET: http://opensolaris.org/os/community/testing/testsuites/ctifortet/
CTI framework is recommended for creating new test suites. See discuss thread: http://www.opensolaris.org/jive/thread.jspa?threadID=67101&tstart=0
- CTI for TET - Common Test Infrastructure for TET: http://opensolaris.org/os/community/testing/testsuites/ctifortet/
- Shell coding style guidelines: http://www.opensolaris.org/os/project/shell/shellstyle/