No 1: Difference between Validated and NonValidated:

(1)   Validated System------Closed System

(2)   Non Validated------Open System

 

No 2: Which rulers does validated system contain?

(1)   Every user has to be unique

(2)   Every signature should be unique identified

(3)   Every record has two signature (autor and reviewer)

 

No 3: How to manage validated system?

(1)   Administratered

(2)   Audit Trail

(3)   Person are trained

(4)   Individuals are responsible

(5)   Data cann’t be manipulated

(6)   Reproducible

 

No 4: Which method does Validated system use?

(1)   Include screen shot in every resulting step

(2)   Convert finalized test case to PDF

(3)   Print out

(4)   Which way execute Test Case

 

No 5: How to create the protection for PDF?

(1)   Install Security Add-in

(2)   File--->Document--->Security---->Certificate Security---->Save these settings as policy

(3)   After creatig protection, you can click “sign”---->”autor”/”reviewer”, and then you can change or write review comments

 

No 6: Where identifies “Validated/Non Validated”?

(1)   21 CFR (part 11), CFR is the abbreviation of “Code of Federal Regulation”, it is created in 1999 by Cliton

(2)   FDA------Food & Drug Administrator

(3)   21 CFR (part 11) is about electronic signature & Elec Records

No 1: What does BA do initially?

(1)   Interview users

(2)   Gather requirements--->mainly on functional requirements

(3)   Design specification

(4)   Functional specification, like user case

(5)   SME--->Subject Matter Experts

 

No 2: What does BA do in next interview?

(1)   Interview

(2)   Defects & Enhancement

(3)   Functional Enhancement & Priorities

(4)   UATS

(5)   Training

 

No 3: What is BA’s skill?

(1)   Communication (Document)

(2)   Domain knowledge

(3)   Training

(4)   Analysis & Summary

(5)   Has to be a good listener

 

No 4: What is BA responsibility for?

(1)   Document

(2)   Consistant communication & clarification

(3)   Bridge between customer & development

(4)   Conduct JAD(Junit application Design) session

(5)   Gather requirements

(6)   User Case

(7)   Prototypes

 

No 5: Which technology skiils does BA master?

(1)   MS word (Document ability)

(2)   UML (Drawing tool)

(3)   Excel

(4)   Prototype tools (Axure RP Pro v4.4.1.745, EnterpriseArchitectv7.0.816, ER studio 7.0.1 and so on)

 

No 6: What is prototype?

(1)   What I hear, I forget

(2)   What I see, I remember

(3)   What I do, I understand

-------Lao Tse

No 7: Which kinds of tools for designing user case?

(1)   Open source: StartUML, Umbello--->Linux, AndroMDA, BOUML, ArgoUML

(2)   Licensed Tools: MS Visio, Rational Rose, Visual Paradign, SmartDraw, etc...

 

No 8: UML must contain three components:

(1)   Actor

(2)   Include/extend

(3)   Use case

No 1: We can look for Open-Source Tool for testing from the following web site:

(1)   www.opensourcetesting.org

 

No 2: Open-Source testing tool:

(1)   Selenium, it is a functional testing tool, and suit for agile testing. Its’ advantage: IDE, Core, Remote Control; Its’ disadvantage: limited support, it base on FireFox Web browse

(2)   QATraq, testing management tool

No 1: Before we start to do performance testing, we need do the following things:

(1)   Plan

(2)   Identify trouble points (Bottlenecks)

(3)   Identify the hardware

(4)   Identify the technology

 

No 2: If we do performance testing for web page, we should clean cookies before testing.

 

No 3: There are two kinds of services:

(1)   Web service: Apache

(2)   Application service: WebLogic, WebSphere

 

No 4: Performance testing, usually, we check the following points:

(1)   Hits/second

(2)   Throughput: how much pages be sent to service

(3)   Response Time: t1+t2+t3+t4; If there isn’t web service,then it is equal to t5+t6

(4)   Number of register user

(5)   Number of transaction record

 

No 5: How to use WebLoad to do performance testing? You can refer to the following steps:

(1)   Creating and editing scripts

(2)   Creating & running Load test

(3)   Analyzing load test results

 

No 6: In result report, the results is passed, however, there is problem, why we say like that?

(1)    “Passed” status means that the action has finished, however, there is issue in performance.

(2)    Choose “goal-oriental” model, and then create checkpoint

 

No 1: Create test sets for one application system, you can do as the following:

(1)   Regard one page as one application screen

(2)   Regard one section of one page as child group

(3)   Create test case in each group

 

No 2: When we test Financial Website, we must consider the following three points:

(1)   Testing session, for example: clicking “back” key

(2)   Checking whether can add user information page into favorite, for example: login financial system, and then add some page into favorite. If can be added, it is a bug.

(3)   Testing security

No 1: As a QA leader, if you need QC to manage testing work, you can do as the following:

(1)   Creating project in QC Site Administration

(2)   Setting up groups in QC Tool Customization

(3)   Adding users to group

(4)   Adding fields in QC

(5)   Importing Requirements

(6)   Maintaining clarification logo

 

No 2: QTP object repository usually likes the following:

(1)   There are two kinds of object repository: local and share

(2)   Object repository framework: common object repository, common script, common parameter

(3)   Object repository Library: Pro object repository, Pro test script, Pro test parameter

 

No 3: If you have built connection between QTP and QC, however, QTP script. cann’t run in QC, you can do as the following:
(1) In QTP, clicking “Tools”--->”Options”--->”run”

(2) In “run” page, checking on “Allow other Mercury products to tests and components”

(3) In QC, run QTP scripts again

 

No 4: Create project template in QC Site Administration

(1) In browse address, input “http://XXX.XXX.XXX.XXX:8080/qcbin/”

(2) Clicking “Site Administration”, and open “Site Administration” page

(3) Selecting one domain

(4) Clicking “Create Project”, then you can set fields and save it as project template

 

No 5: Identify testing process by QC; you can identify some fields if you need.

(1)   Requirement, before import requirements, we need to add these fields:

1’ out of scope---value (review status)

2’ application screen---field (parent/group name, filter nonrequirements)

3’ change priority---value, opposite to defect’s priority (1-urgent....5-low)

4’ review comment

5’ Release

(2)   Test Plan, before making test plan, we need to add these fields:

1’ peer review

2’ Developer review

3’ sign off

4’ assigned

5’ reviewer

6’ comments

7’ version

8’ automatic---Y/N

9’ Application Screen

10’ priority

(3)   Test lab, before executing test case, we need to add these fields:

1’ environment---field, it contains these values: test, stage, development, production

2’ Instance

(4)   Defect, if we need, we can add these fields:

1’ reviewer

2’ enhancement---Y/N

3’ assigned by

4’ group, it contains: Developer, tester, user

 

No 6: Who manage requirements?

(1)   BA manage requirements

(2)   QA can review it

(3)   QA cann’t remove requirement

 

No 7: How to distribute permission to each group?

(1)   tools--->customization--->set up groups

(2)   choose one group, click “view” button

(3)   click “defect”, select “status”, you can change the transition rules of status

 

No 8: How to create test lab?

(1)   Create test set

(2)   Click “Select Tests” and select “test case”

(3)   Click “Add tests to test set”

 

No 9: How to create test plan tree?

(1)   Usually, we set up these groups in test plan: release, regression, automated, removed

(2)   We use control no(010...) to identify different level

(3)   We can do as the following figure:

No 1: If you need special fields for requirements which don’t exist in system default fields, you can do as the following:

(1)   Clicking “Tools”--->”Customize”

(2)   Clicking “Customize Project Entities”

(3)   Opening “Requirement”--->”User Fields” folder

(4)   Clicking “New field” button at the bottom of the page

(5)   In the “New field” page, inputing “Field Lable” what you want

(6)   If select “Field Type” which is “lookup list” type, then it will display “Lookup List” page. And then you can do the following:

1’ If it has existed the list what you want in the drop-down list, you can select it and click “save” button;

2’ If it has existed the list name what you want in the drop-down list, however, you need to change the fields of the list, you can click “goto list” and click “New Item”, then save it;

3’ If there isn’t the list what you want, you can click “New List” button.

 

No 2: If you need to change “Project List”, how do you do? You can do as the following:

(1)   Clicking “Tools”--->”Customize”

(2)   Clicking “Customize Project List”

(3)   Selecting the list name in the “Lists” drop-down list

(4)   If you need, you can click “New Item” button to add some items

(5)   If you need a new list, you can click “New List”

Usually, these lists can be used in every component (Requirements, Business Components, Test plan, Test lab, Defects)

Question: If there are many defects, should we fix high priority defect or severity defect?

In my opinion, we should fix the higher severity defects. Because this kind of defects would affect system running and testing schedule, the other reason is that we identify the priority according to severity. The defect is more serious, its’ priority level is higher.

Pathik’s answer: It maybe higher severity or higher priority, that depends on person. If he is the customer, he should like to fix the higher priority defect. Because he think the higher priority feature is important. If he is the developer, he need to fix the higher severity defect, because it will affect the system’s running and testing. That is to say, fixing which kind of defect first, it depends on situation.

Usually, customer identifies the priority like that: the feature is more important, the priority is higher. However, in development team, we used to identify the priority like this: the severity is higher, the priority is higher, and we would fix defect according to the priority.