FYI Center :: Forum

Any more information on how to start QA within Testing enviroment 2? [by luck]

Tue, 24 Nov 2009 00:32:20

SQA Career Center:: Any more information on how to start QA within Testing enviroment 2?
Any more information on how to start QA within Testing enviroment 2?

Assuming you are talking about QA and not QC, following is a post I
made in another group some months ago. Hope this information is
somewhat useful.

Following are some steps you can use to kick start the process:

1] Create a formal group in your organization that you can call as
"SEPG (Software Engineering Process Group)" or "Process Engineering
Committee" or something like it.

2] Try to enlist the services of the highest management person that you
can get to agree and make him the committee head. This will ensure that
the seriousness of your efforts is clearly conveyed to other employees
in the organization.

3] Identify the various persons in your organization who are subject
matter experts in their field of work & try to make them members of the
committee.

4] Identify the processes in your organization that you would like to
improve

5] Create subcommittees or subgroups that will have the responsibility
of creating the standards for those processes. Depending on how many
persons you are able to include in your SEPG or PEC, many subgroups can
be formed simultaneously. Make sure that the group creating the
standards for a process has a member from the group of users who will
actually use the process.

6] Once the subgroups create the standards and it is approved by the
management, implement it on a pilot project or part of a project.

7] After the process has been live for some time, determine the
benefits that have been achieved. If no benefits are visible, go back
to the drawing table and modify the process.

8] If benefits are clearly visible, rollout the process improvement
across the whole project & them across the organization.

Please remember the following:
1] It is extremely important to have the management commitment for any
Process improvement projects to be successful.
2] You should make an effort to identify and "advertise" the benefits
of PI to all employees across your organization.

SDET question: What does following code do , if we pass head pointer of a link list. [by luck]

Mon, 16 Nov 2009 21:12:18

SQA Career Center:: SDET question: What does following code do , if we pass head pointer of a link list.
What does following code do , if we pass head pointer of a link list.

void list( struct node * head)
{
if(head)
{
list(head->next);
printf("%d",head->value);
}
}

Answers:

prints link list in reverse order.

Any more information on how to start QA within Testing enviroment? [by luck]

Mon, 09 Nov 2009 22:34:08

SQA Career Center:: Any more information on how to start QA within Testing enviroment?
Any more information on how to start QA within Testing enviroment?

Well, remember that that the purpose of a QA department is different
than a QC (Quality Control) or testing department. A QA group would be
responsible for tasks like:
- Verify everyone follows the established SDLC process, which means
establishing checkpoints that must be verified before the project
progresses to the next phase in the SDLC.
- Verify that the documentation that is provided is correct and
complete and is updated when changes are made to the requirements or
design (this can be accomplished with reviews or formal inspections of
a sampling of the documentation provided, including requirements,
design and test documentation)
- Verify that all the documentation that should be provided is
provided at the correct stages in the project (this really should be
part of the checkpoints I mentioned before)
- Verify that as the code is written according to any documented
standards that you have (this can be accomplished by doing code
walkthroughs along the way).

If your group is just starting, I would implement a portion of this and
get people used to the idea and add to it as projects complete. Just
don't forget to do lessons learned sessions after each project
completes. It is a very important step that keeps people involved in
the project feeling that they are part of the process, not controlled
by the "QA police".

Check list for Conducting Unit Tests [by luck]

Mon, 02 Nov 2009 22:18:54

SQA Career Center:: Check list for Conducting Unit Tests
Check list for Conducting Unit Tests

� Is the number of input parameters equal to number of arguments?
� Do parameter and argument attributes match?
� Do parameter and argument units system match?
� Is the number of arguments transmitted to called modules equal to number of parameters?
� Are the attributes of arguments transmitted to called modules equal to attributes of parameters?
� Is the units system of arguments transmitted to called modules equal to units system of parameters?
� Are the number of attributes and the order of arguments to built-in functions correct?
� Are any references to parameters not associated with current point of entry?
� Have input only arguments altered?
� Are global variable definitions consistent across modules?
� Are constraints passed as arguments?
� When a module performs external I/O, additional interface tests must be conducted.

Again, from Myers:
� File attributes correct?
� OPEN/CLOSE statements correct?
� Format specification matches I/O statement?
� Buffer size matches record size?
� Files opened before use?
� End-of-file conditions handled?
� I/O errors handled?
� Any textual errors in output information?
The local data structure for a module is a common source of errors. Test cases should be designed to uncover errors in the following categories:
� improper or inconsistent typing
� erroneous initialization or default values
� incorrect (misspelled or truncated) variable names
� inconsistent data types
� underflow, overflow and addressing exceptions
From a strategic point of view, the following questions should be addressed:
� Has the component interface been fully tested?
� Have local data structured been exercised at their boundaries?
� Has the cyclomatic complexity of the module been determined?
� Have all independent basis paths been tested?
� Have all loops been tested appropriately?
� Have data flow paths been tested?
� Have all error handling paths been tested?

How to validate password with regular expression [by luck]

Mon, 26 Oct 2009 19:00:30

SQA Career Center:: How to validate password with regular expression
How to validate password with regular expression

((?=.*\d)(?=.*[a-z])(?=.*[A-Z])(?=.*[@#$%]).{6,20})

Description

* ?= � means apply the assertion formula, meaningless by itself, always work with other combination.
* . � means any characters except new line �\n�
* * � means length can be zero or more
* () � grouping
* (?=.*\d) � \d means digit from 0-9. Only digit is allow here.
* (?=.*[a-z]) � [a-z] means lowercase characters from a to z. Only lowercase characters is allow here.
* (?=.*[A-Z]) � [A-Z] means uppercase characters from A to Z. Only uppercase characters is allow here.
* (?=.*[@#$%]) � [@#$%] means special character �@#$%�. Only special characters �@#$%� is allow here.
* {6,20} � the length of the string, minimum characters is 6, maximum characters is 20.

Whole combination is means, 6 to 20 characters string with at least one digit, one upper case letter, one lower case letter and one special symbol (�@#$%�). This regular expression pattern is very useful to implement a strong and complex password.

P.S The grouping formula order is doesn�t matter.

BVA or EP where and how exactly this should be used? [by luck]

Mon, 19 Oct 2009 23:35:55

SQA Career Center:: BVA or EP where and how exactly this should be used?
BVA or EP where and how exactly this should be used?

Boundary Value Analysis or Equivalence Partitioning, is this technique used for Functional Testing or Validation Testing? Its understood that it is used to prepare test data. But that test data will be validating
a field alone or used along with functional TC?

A

Boundary Value Analysis or Equivalence Partitioning is the technique used
for functional testing. Equivalence partitioning is dividing of input range
into partiitions of equivalence classes, so that one test case can cover the
whole partition. For example if there is a validation for month field input
ranges from 1 to 12. We divide this range into valid and invalid ranges.
There is arange below 1 and there is a range in between 1 and 12, and there
is a range above 12. If we check for any value in the particular ranges the
test case will be sufficient to check the validation.
so three test cases can cover this task in case of equivalence partitioning.
Boundary Value Analysis:This is just an enhancement of equivalencer
partitioning. In this we test on, just below the boundaries. In case of
month validation if we don't test theboundaries properly it may not accept 1
and 12 in case if the developer has forgotten the equivalent sign. Hence on
boundary value analysis test cases are written on the boundaries.

There are 6 test cases in case of boundary value analysis. They are 0,1&2
for the left boundary and 11,12&13 for the right boundary.

Windows Security Business Unit [by luck]

Mon, 12 Oct 2009 23:53:35

SQA Career Center:: Windows Security Business Unit
Windows Security Business Unit

Ques 1. To write a C++ function to copy one file to another and test it Ques2. Write the following code in C and test it.

Char * converLabel(int iData)

Given: iData > 0

If iData = 1 � char * = "A"; 2 � "B; ��.. 26 = 'Z',

27 = 'AA",��."ZZ"

52 = "BA"� "BZ"

then 52+25 = "CA"�

.."ZZ"

."AAA"

"AAB"

..

"ABA"..

..AAAAZ...

until 2^15..

Ques 3. Explain about Domain Controller in Windows?

Ques 4. What are various security features provided in Windows?

Ques on C# and C++ like Virtual functions and virtual table.

Test Cases & Test Scenario's Examples [by luck]

Mon, 05 Oct 2009 21:22:16

SQA Career Center:: Test Cases & Test Scenario's Examples
Test Cases & Test Scenario's Examples

Example1 : Below is sample Registration form contains two input fields and submit button. Validations are given below.

Examples of field validation criteria are:

* First and last name fields are required.
* First and last name fields are limited to 50 characters each.
* First and last name fields will not accept numbers.
* First and last name fields will not accept the following characters: `~!@#$%^&*()_:";'{}[]+<>?,./

Consider the following example:

Test Cases and Test Scenarios Examples.JPG

Here�s a set of test scenario's that include validation criteria:

1.
Launch an IE browser and go to the Registration Form.
2.
Verify the registration page opens.
3.
On the registration page, click the mouse in the First Name field.
4.
Leave the First Name and Last Name fields blank and click on the Submit button.
5.
Verify an error message appears saying you cannot leave the First Name and Last Name fields blank.
6.
Enter 50 chracters in both the First and Last Name fields.
7.
Verify the names are accepted.
8.
Enter more than 50 chracters in both the First and Last Name fields.
9.
Verify an error message appears saying you cannot enter more than 50 characters in the First Name and Last Name fields.
10.
Enter numbers in the First and Last Name fields.
11.
Verify an error message appears saying you cannot enter numbers in the First and Last Name fields.
12.
Enter the chracters "`~!@#$%^&*()_:";'{}[]+<>?,./" in the First and Last Name fields.
13.
Verify an error message appears saying you cannot enter "`~!@#$%^&*()_:";'{}[]+<>?,./" characters in the First and Last Name fields.
14.
Type �John� in the First Name field.
15.
Click the mouse in the Last Name field.
16.
Type in �Doe� in Last Name field.
17.
Click on the Submit button.
18.
Click on registration List in the left nav bar.
19.
Verify the Name �John Doe� is now present in the registration list.

Press Read More Button for test cases for this scenarios

Even the above set of test cases takes a few shortcuts by testing validation on both fields at once. A more correct way to do it would be to test the field validation independently.

For example, the blank name validation should be tested like this:

1. Leave the First Name and Last Name fields blank and click on the Submit button.
2. Verify an error message appears saying you cannot leave the First Name and Last Name fields blank.
3. Enter a valid First Name and leave the Last Name field blank and click on the Submit button.
4. Verify an error message appears saying you cannot leave the Last Name field blank.
5. Enter a valid Last Name and leave the First Name field blank and click on the Submit button.
6. Verify an error message appears saying you cannot leave the First Name field blank.

As you can see, this increases the number of test cases needed substantially, and even this set of test cases leaves certain issues untested.

Sample format of TestCase Document:


<table bordercolor="black" cellspacing="0" cellpadding="4" width="460" align="left" bgcolor="white" border="1">
  <tbody>
    <tr>
      <td><p><strong>Case Number</strong> </p></td>
      <td><p><strong>Action</strong> </p></td>
      <td><p><strong>Expected Results</strong> </p></td>

      <td><p><strong>Actual Results</strong> </p></td>
      <td><p><strong>Pass/Fail</strong> </p></td>
    </tr>
    <tr>
      <td>2.1.0</td>
      <td colspan="4"> <div align="center"><strong>Blank Check </strong></div></td>

    </tr>
    <tr>
      <td><p>2.1.1 </p></td>
      <td><p>Entry with a blank First Name. </p></td>
      <td><p>An error message is displayed saying The First Name must be   filled in. </p></td>
      <td></td>
      <td></td>

    </tr>
    <tr>
      <td><p>2.2.0 </p></td>
      <td colspan="4"><p align="center"><strong>Maximum Characters </strong></p></td>
    </tr>
    <tr>
      <td><p>2.2.1 </p></td>

      <td><p>The First Name field will accept a maximum of 50 characters. </p></td>
      <td><p>The First Name field should accept a maximum of 50 characters. </p></td>
      <td></td>
      <td></td>
    </tr>
    <tr>
      <td></td>
      <td></td>

      <td></td>
      <td></td>
      <td></td>
    </tr>
  </tbody>
</table>

Interview questions on WinRunner [by luck]

Sat, 19 Sep 2009 02:12:47

SQA Career Center:: Interview questions on WinRunner
Interview questions on WinRunner

1. How you used WinRunner in your project? - Yes, I have been using WinRunner for creating automated scripts for GUI, functional and regression testing of the AUT.
2. Explain WinRunner testing process? - WinRunner testing process involves six main stages
* Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
* Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you want to check the response of the application being tested.

* Debug Test: run tests in Debug mode to make sure they run smoothly
* Run Tests: run tests in Verify mode to test your application.
* View Results: determines the success or failure of the tests.
* Report Defects: If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window.
3. What is contained in the GUI map? - WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object�s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description. There are 2 types of GUI Map files. Global GUI Map file: a single GUI Map file for the entire application. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.
4. How does WinRunner recognize objects on the application? - WinRunner uses the GUI Map file to recognize objects on the application. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object�s description in the GUI map and then looks for an object with the same properties in the application being tested.
5. Have you created test scripts and what is contained in the test scripts? - Yes I have created test scripts. It contains the statement in Mercury Interactive�s Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner�s visual programming tool, the Function Generator.
6. How does WinRunner evaluate test results? - Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.
7. Have you performed debugging of the scripts? - Yes, I have performed debugging of scripts. We can debug the script by executing the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.
8. How do you run your test scripts? - We run tests in Verify mode to test your application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier. If any mismatches are found, WinRunner captures them as actual results.
9. How do you analyze results and report the defects? - Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window. If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window. This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed.
10. What is the use of Test Director software? - TestDirector is Mercury Interactive�s software test management tool. It helps quality assurance personnel plan and organize the testing process. With TestDirector you can create a database of manual and automated tests, build test cycles, run tests, and report and track defects. You can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.
11. Have you integrated your automated scripts from TestDirector? - When you work with WinRunner, you can choose to save your tests directly to your TestDirector database or while creating a test case in the TestDirector we can specify whether the script in automated or manual. And if it is automated script then TestDirector will build a skeleton for the script that can be later modified into one which could be used to test the AUT.
12. What are the different modes of recording? - There are two type of recording in WinRunner. Context Sensitive recording records the operations you perform on your application by identifying Graphical User Interface (GUI) objects. Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.
13. What is the purpose of loading WinRunner Add-Ins? - Add-Ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those functions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function.
14. What are the reasons that WinRunner fails to identify an object on the GUI? - WinRunner fails to identify an object in a GUI due to various reasons. The object is not a standard windows object. If the browser used is not compatible with the WinRunner version, GUI Map Editor will not be able to learn any of the objects displayed in the browser window.
15. What is meant by the logical name of the object? - An object�s logical name is determined by its class. In most cases, the logical name is the label that appears on an object.
16. If the object does not have a name then what will be the logical name? - If the object does not have a name then the logical name could be the attached text.
17. What is the different between GUI map and GUI map files? - The GUI map is actually the sum of one or more GUI map files. There are two modes for organizing GUI map files. Global GUI Map file: a single GUI Map file for the entire application. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.

GUI Map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description.
18. How do you view the contents of the GUI map? - GUI Map editor displays the content of a GUI Map. We can invoke GUI Map Editor from the Tools Menu in WinRunner. The GUI Map Editor displays the various GUI Map files created and the windows and objects learned in to them with their logical name and physical description.
19. When you create GUI map do you record all the objects of specific objects? - If we are learning a window then WinRunner automatically learns all the objects in the window else we will we identifying those object, which are to be learned in a window, since we will be working with only those objects while creating scripts.

With a login window, what are all called to be a GUI test, functional test and security test? [by luck]

Sat, 12 Sep 2009 03:14:54

SQA Career Center:: With a login window, what are all called to be a GUI test, functional test and security test?
1. With a login window, what are all called to be a GUI test,
functional test and security test?
2. If an application allows logging in an unregistered user or a user
with wrong password, is it a functional bug or security bug?

A:
GUI : the screen contains username, password labels, corresponding text
box, buttons OK, and CANCEL. these components are available in this
part of the page say left ,right middle etc

Functional : When the fields are entered correctly or incorrectly and
Ok button is clicked. It should navigate to corresponding screen or
error page.

Security : The user shld be logged in only for correct username &
password, otherwise rejected.

So the condition you have mentioned is Security bug. Validation is not
been taken care of.

--------
Basically, If an application allows logging in an unregistered user or a
user
with wrong password, it would be a *Functional bug*.

The *reason* behind that is: You would have a requirement covering this
functionality i.e., when the user gives a valid id and password, the system
should allow him to log in into the application.

So, when you are testing this requirement, it will fail if you give an
invalid id and password. So the functionality mentioned does not hold true
and hence it is a functionality bug.

-------
I understood your point.
But still when the button is clicked the screen shld navigate to
another page.
The resulting page may be a error page or a corresponding home page for
that user.

The functionality is whether the page is navigating when the button is
clicked.

In this case its navigating to the page, but it is not checking for the
valid ID, Pwd.

So, It is not a functional bug. And i think it is a security bug.

If the case i have mentioned is incorrect.
WHAT IS A SECURITY BUG?
Give an illustration so that i understand. Will U?