2018年8月10日金曜日

テスト計画書 サンプル


新しいWikiページ 編集 ウォッチ ロック 名前変更 削除 履歴
Wiki »

KISA for NIFTY (MR15) Test Plan

Document Information

2018/01/29
Product Management: Yuichi Arata
Quality assurance: Momoko Furukawa
(Template version: v2.5)

Introduction

This release purpose is that for support new Android OS 8. The customization build for xSP partner based standard KIS for Android Japan MR15.

Testing Policy

Prerequisite

Standard functions, defeats and restrictions are same with standard version.
Functional testing is already tested on standard build. Customization build made based on standard Japanese MR15.
Web portal is used with Anti-Theft web portal, Not used with My Kaspersky.
Help contents are customized manually according to spec by KLJ TAM.

Policy

Testing performed for customization points according to customization specification document.
No testing covered full function area. Minimized functional testing is performed that is same as acceptance testing.
No testing as technical review for online help contents.

Target Products

Kaspersky Internet Security for Android (MR15) for NIFTY
Anti-Theft Portal http://anti-theft.kaspersky.com/

Non-Targeted Products

My Kaspersky https://my.kaspersky.com/

Project milestone

Milestones Date Owner
Meeting for Project Feasibility Judgment N/A PMM
Product Development team Kick-Off 2018/1/19 PM
Meeting for the Test Plan 2018/1/29 PM
Deadline for Bugs to be Reported 2018/2/14 PM
Linguistic green light 2018/2/28 Doc&Loc Manager
User acceptance testing (UAT) 2018/3/1-7 TAM
JP RTT 2018/3/8 PM
Meeting for Product Quality Judgment 2018/3/12 PM
JP TR 2018/3/19 HQ

GTM testing requirement

  1. Make sure that build customization according to specification attached on Change Request.
    1. Change Request 2335008:[CR][Android] KISA MR15 for Nifty
      1. Specification: KIS4Android_RebrandingSpecification_NIFTY_MR15_20171130_PM_reviewed.docx
        1. UPDATED: KIS4Android_RebrandingSpecification_NIFTY_MR15_20171130_PM_reviewed_TS20180125_PM.docx
      2. Graphics: Grapchics_KISAMR15_NIFTY_20171116.zip
      3. EULA: /depot/EULA/KISA/Customizations/Nifty/MR15/ja/license.html
  2. Web Portal
    1. Make sure that device can be connected to Anti-Theft Web Management Portal (ATWM). Not use My Kaspersky.
    2. Make sure that user can control device from ATWM.
    3. Make sure that user can change the password from ‘Forgot your password?’ on UI of Sign in to portal.
  3. External links
    1. Make sure that user can open online-help for NIFTY MR15 from product external links.
  4. EULA/KSN statement
    1. Make sure that EULA is replaced NIFTY version.
    2. Make sure that KSN statement is NOT replaced from standard version.
  5. Skip lite mode activation on first run wizard.
  6. Make sure that user must activate product with their NIFTY activation code.
  7. Change the period that activation status changed to be lite mode automatically if device disconnected from internet.
    1. Make sure that to not be changed to lite mode after 30 days from disconnected internet.
    2. Make sure that be changed to lite mode after 90 days from disconnected internet.
    3. Make sure that user can activate again with NIFTY Activation code from UI after changed to lite mode.
  8. Upgrade
    1. Make sure that user can upgrade from previous custom build MR12.
  9. Incompatible packages
    1. Make sure that to detect incompatible package when install custom build with active installation of standard build.
    2. Make sure that to detect incompatible package when install custom build with active installation of other custom build (KISA for KDDI).

Project risk

Risk Counterplan
Delay the build deliver for QA KLJ PM have to negotiate enough with HQ TAM about schedule before starting test term
Many bugs found on QA testing and UAT KLJ PM have to make an arrangement to change new date appropriately, KLJ TAM will communication in timely manner with customer

Testing criteria and release criteria

  1. Covered all GTM testing coverage
  2. No stop bugs
  3. Any detected issues should be analyzed and discussed, and all issues to be raised in bug database (TFS and Redmine)
  4. Known issues are clearly defined and all potential risks are explained and agreed with other related departments
  5. All testing items described in testing scope to be covered

Test type and scope

Test type

  • Functional: Functional test.
  • L10N: Japanese translation test of Explanation on GUIs, messages and Online Help.
  • GUI: Checks of truncation on GUIs and the shaping of the layout.
  • Upgrade: Upgrade test from an older product or an older version of the same product.
  • Bug Regression: Regression test on bugs which have been checked for correction.
  • Final Certification: Final certification test against builds which are candidates for release.

Test scope

Yes In-scope for testing
No Out-of-scope for testing
L10N/GUI will be checked in any section DocLoc, QA by HQ, KLJ
Categories Test areas Redmine tasks Test types Notes
Functional L10N GUI Final Certification
Rebranding Specification for Rebranding KIS4Android_RebrandingSpecification_NIFTY_MR15_20171130_PM_reviewed.docx YES YES YES NO
Basic function (Rebranding Specification) Compatibility(KISA, KDDI) YES YES YES NO
Upgrade YES YES YES NO
Handover settings - NO NO NO NO
License compatibility YES YES YES NO
EULA and KSN statement YES YES YES YES
External link NO YES YES NO
Portal cooperative YES YES YES NO
Besic Funtion Install/Uninstall YES YES YES YES
Default setting value check - NO YES YES NO
Scan YES YES YES YES
Update YES YES YES YES
Real-time protection - NO YES YES NO
Call & text filter - NO YES YES NO
Anti-theft - NO YES YES NO
SMS confirmation & controle & funtional notification - NO YES YES NO
Web protection - NO YES YES NO
Privacy protection - NO YES YES NO
Additonal settings - NO YES YES NO
Management via warable devices YES YES YES YES

Test schedule

Phase Milestones, tasks Date Expected hours (MH) Notes
Plan Product development team Kick-Off 2018/1/19 1
Create Test Plan 2018/1/23-24 2
Meeting for the Test Plan 2018/1/29 Mail review
Preparation Create Test case 2018/1/24-30 7.5
Prepare the Test Environment 2018/1/30 0.5
Implement Basic function (Rebranding Specification) 2018/1/31-2/6 30
Due date to submit must-fix bug list to HQ 2018/2/14
Bug Regression Test 2018/2/27-28 4
Linguistic green light 2018/2/28
Final Certification Test 2018/3/8 4
JP RTT 2018/3/8
Report Create test report 2018/3/8-3/9 2
Meeting for Product Quality Judgement 2018/3/12 Mail review
JP TR 2018/3/19
Postmortem
Total 51

Testing environment

System requirements

  • Conform to standard version. Android 4.4-8.0
  • Include verification on the tablet device for confirmation of the GUI.

Environment set

Smartphone
Set# Carrier DeviceName OS Browsers QA management device Notes
1 - Nexus 6P 8.0 Chrome #8106 Full test is not only this device. Disperse to test cases with other device.
2 Y!Mobile Android One X1 7.1.2 Chrome #21612 Full test is not only this device. Disperse to test cases with other device.
3 Softbank Sony Xperia Z5 501SO 6.0. Chrome #8011 Device for bug survey.
4 au Xperia Z2 SOL25 5.0.2 Chrome #2634 Device for bug survey.
5 Docomo Xperia Z SO-02E 4.4.2 Chrome,Default browser #3366 Device for bug survey.
Tablet
Set# Carrier DeviceName OS Browsers QA management device Notes
1 - Nexus 9 7.0. Chrome #3942 Confirm to Tablet UI only.
Wearable
Set# Carrier DeviceName OS Browsers QA management device Notes
1 - CASIO:WSD-F10RG 7.1.1 - #10691 Confirm to Final Certification only.

Planned deliverables

Deliverables Assigned to Due date
RTT Build HQ 2018/3/8
EULA PM/TAM
KSN statement - -
Test plan PM 2018/1/29
Test cases QA Lead 2018/1/30
Test report PM 2018/3/12
Deferred bug list QA Lead 2018/3/12
Won’t fix bug list QA Lead 2018/3/12
External URL list QA Lead 2018/3/12

Stakeholders

Development team

KLJ:
Role Member
Product Manager Yuichi Arata
Technical Product Manager Tomomasa Sato
Doc&Loc Manager Tomonori Imada
QA Lead Momoko Furukawa
Tester Momoko Furukawa
HQ:
Role Member Notes
Head of Products Testing Olga Nikolenko
Product Manager Oleg V. Nevstruev
Project Manager Sergey Kochanov
Head of Products Victor Yablokov
Doc&Loc Manager Dmitry Bentsa
*Project Manager… Basically prohibited to contact directly from KLJapan.

Other departments

Department Team Member Notes
CSMO Product marketing Yoshinori Tamura
Product Consumer Support Yuichi Kimura
Corporate business Engineering Tomomasa Sato
Corporate business Alliance sales Daisuke Kuroda
CEO Moscow Liaison Denis Chernov

Project information management

Redmine

Information on testing and bugs will be managed on Redmine.
Rebrand Products » KISA Rebranding » KISA MR15 Rebranding »KISA for NIFTY (MR15)
https://productqa.jp.kaspersky.net/redmine/projects/kisa-for-nifty-mr15

PMWiki

https://pmwiki.jp.kaspersky.net/wiki/index.php/KISA_MR15_for_NIFTY

FileServer

For file-sharing within the QA group
\\qateamsvr\depot\qa\build\KISA Rebranding\NIFTY\MR15

Build management

Build management rule

KLJ

For QA team
\\qateamsvr\depot\qa\build\KISA Rebranding\NIFTY\MR15
To share builds with other departments
\\kavfs\kaspersky\dev\Software\Japanese\product\KIS_for_Android_Rebranding\MR15\NIFTY\pk
TR build
\\kavfs\product_packages\Rebranding\NIFTY\KISA\MR15_[VERSION]

Build creation

BuildManagementRule

Testing case management

Manage all test cases on LocalTFS.
Project: KISA
https://jplocaltfs2.apac.kaspersky.com/tfs/DefaultCollection/KISA
NIFTY: KISA for NIFTY MR15 (Id: 21841)
https://jplocaltfs2.apac.kaspersky.com/tfs/DefaultCollection/KISA/_testManagement#planId=21841&suiteId=21842&_a=tests

Incident management

HQ

Submit bug reports on TFS.
https://hqrndtfs.avp.ru/tfs/DefaultCollection/Mob-KISA
Area:Mob-KISA\Customizations\Partners\Nifty
Iteration path:Mob-KISA\Customizations\MR15\MR15 for Nifty
Bug report guidelines： http://productqa.kaspersky.co.jp/redmine/attachments/download/2090/Defects.docx

KLJ

Submit bug reports on Redmine.
Redmine bug report guidelines
Bug workflow
GUI/L10N issue categories

Bug priority

BugPriority

Testing guideline

Test_Guideline

Actual evaluation indicators and Execution control plans

  • Project Report is posted to forum
  • Test tasks are controlled with Redmine tickets
  • Test progress is calculated based on progression rate of Redmine tasks, posted to Wiki
  • Test progress measured on Excel, compared with the progress day average.
    • \\kavfs\kaspersky\dev\PM\Project_Progress\2018_QA_KISA_MR15_NIFTY.xlsx
  • PM/QA/D&L triage, prioritize and decide severities of the bugs on weekly meeting
    • if required meeting can be daily basis
  • Members swiftly report any other significant problem affecting progression of the project to PM
  • PM shares info of the bugs to stake holders depending on their impacts

History

v1.0 Initial
他の形式にエクスポート: PDF HTML TXT

投稿者 時刻:

0 件のコメント:

コメントを投稿

登録: コメントの投稿 (Atom)