Practice Paper - 3

Question 21:
A test plan is prepared for management by the project leader, which explains all project control variances relative to the testing effort. It also summarizes test case logs and coverage statistics for key programs.
A. True
B. False

Question 22:
Memory leak checker tools are used to create runtime performance profiles at the module, library and function level.
A. True
B. False

Question 23:
Configuration management tools support activities related to managing the environment, including configuration management, change control, library control, documentation control.
A. True
B. False

Question 24:
The key process area at CMM Level 4 - Managed focus on establishing a quantitative understanding of both the software process and the software work products being built.
A. True
B. False

Question 25:
Non-functional system testing is a testing process that test system requirements that do not relate to functionality.
A. True
B. False

Question 26:
A set of behavioral and performance requirements which, in aggregate, determine the functional properties of a software system.
A. Functional requirement
B. Functional specifications
C. Functional test cases

Question 27:
Business process-based testing is used in system testing and acceptance testing.
A. True
B. False

Practice Paper - 2

Question 11:
Ad Hoc testing is a formal and structured testing method.
A. True
B. False

Question 12:
The programs send bad data to devices, ignore error codes coming back, and try to use devices that are busy or aren't there. This is a:
A. Calculation error
B. Functional error
C. Hardware error
D. System error
E. User Interface error

Question 13:
Errors that are cosmetic in nature are usually assigned a ______ severity level.
A. Fatal (Severity)
B. Low (Severity)
C. Serious (Severity)

Question 14:
If a system is not functioning as documented and the data is not corrupted. What priority and measure are assigned?
A. Priority 1: Critical
B. Priority 2: High
C. Priority 3: Medium
D. Priority 4: Low

Question 15:
A testing process that is conducted to test new features after regression testing of previous features.
A. Operational testing
B. Progressive testing
C. Recovery testing
D. Regression testing

Question 16:
Which of the following are major test documents? (choose the best answer)
a) Test plan
b) Test case
c) Test design
d) Test procedure
e) Defect report
A. a and b
B. a, c, and d
C. a, c, d, and e
D. all of the above

Question 17:
The requirements document identifies all system components and requirements to be tested, as well as detailed approaches to be followed, so that the testing of components and requirements is effective.
A. True
B. False

Question 18:
The test case log is used to keep track of the status of each test case.
A. True
B. False

Question 19:
What test document contains all the information about a specific test case, including requirements and the modules to be tested?
A. Test plan
B. Test case specification
C. Test design specification
D. Test procedure
E. Defect report

Question 20:
A test case specification document is used to keep track of each test run.
A. True
B. False

Practice Paper -1

Question 1:
The best time to influence the quality of a system design is in the __________.
A. Planning Phase
B. Analysis Phase
C. Design Phase
D. Testing Phase

Question 2:
IEEE stands for:
A. Information Engineering Endeavoring to Excel
B. Institute of Electrical and Electronics Engineers
C. Institute of Education for E-commerce Entrepreneurs
D. Individual Excellence in Engineering Enterprises

Question 3:
Which type of document might be reviewed at a Review/Inspection session?
A. Employee performance review
B. Test Plan
C. Project Status Report
D. Defect Tracking Form

Question 4:
Quality control and quality assurance are different names for the same activity.
A. True
B. False

Question 5:
Cause and effect diagrams can be used to view attempts to solving quality issues that have not worked in the past.
A. True
B. False

Question 6:
Which of the following is not a job responsibility of a software tester?
A. Identifying test cases
B. Preparing test data
C. Executing tests
D. Writing the functional specifications

Question 7:
The test strategy that is informal and non structured is:
A. Equivalence partitioning
B. Validation strategy
C. White box testing
D. Ad hoc testing

Question 8:
The test strategy that involves understanding the program logic is:
A. Equivalence partitioning
B. White box testing
C. Black box testing
D. Boundary strategy

Question 9:
Data defects can occur when accessing the programs data log files.
A. True
B. False

Question 10:
Once the requirement document is approved, the Tester can begin creating a Requirements Matrix to track the requirements throughout the SDLC.
A. True
B. False

ISTQB

ISTQB Syllabus

Download area

• ISTQB Constitution V1.1, 17th September 2003
• ISTQB Syllabus Foundation Level V2007, 12th April 2007
• Syllabus Advanced Level, Syllabi
• ISTQB Standard Glossary of Terms used in Software Testing V1.3, May 31st 2007

Archive area

• ISTQB Glossary of Testing Terms V1.0, 8th December 2004
• ISTQB Glossary of Testing Terms V1.1, 29th September 2005
• ISTQB Standard Glossary of Terms used in Software Testing V1.2, 4th June 2006
• ISTQB Syllabus Foundation Level V2005, 1st July 2005

BugTracker.NET

What is BugTracker.NET?

BugTracker.NET is a free, open-source, web-based bug or customer support issue tracker written using ASP.NET, C#, and Microsoft SQL Server (or its free cousins, SQL Server Express and MSDE). It is in daily use by thousands of development and support teams around the world.

BugTracker.NET is easy to install and learn how to use. When you first install it, it is very simple and you can start using it right away. However, it offers you the ability to change its configuration to handle your needs if they are more complex.

Feature Highlights

For detailed info about features, see the BugTracker.NET README.html file. Here are some feature highlights:

Suitable for tracking customer support tickets as well as software bugs.

Sending and receiving emails is integrated with the tracker, so that the email thread about a bug is tracked WITH the bug.

Allows incoming emails to be recorded as bugs. So, for example, an email from your customer could automatically be turned into an bug in the tracker.

Allows you to attach files and screenshots to bugs. There is even a custom screen capture utility [screenshot] that lets you take a screenshot, annotate it, and post it as a bug with just a few clicks.

Add your own custom fields.

Custom bug lists, filtered and sorted the way you want, with the columns that you want.

You can display bugs of a certain priority and/or status in a different color, so that the most important items grab your attention.

Define your own statuses and workflow, or use with the simple one it installs with.

Configure different user roles to see different lists of bugs. For example, a developer might see a list of open bugs. A QA analyst might want to see a list of bugs ready for testing.

Search for bugs using flexible criteria. Save searches as SQL queries that you can run or modify later.

Subscribe to email notifications that tell you when a bug has been added or changed.

Create hyperlinks between related bugs, so that you can jump from one to the other directly.

Includes some starter bug statistic reports with pie charts and bar charts. Easy to create your own reports if you know SQL.

Handles Unicode (Chinese characters, etc...)

Set permissions controlling who can view, report, edit bugs by project.

For more documentation

Source:

Bugzilla 3.0 Released (New Version)

Bugzilla is a open-source Bug tracking tool. Many companies are using this open source tool for managing the software development process.

New Features In Bugzilla 3.0

Custom Fields

Bugzilla now includes very basic support for custom fields.
Users in the admin group can add plain-text or drop-down custom fields. You can edit the values available for drop-down fields using the "Field Values" control panel.Don't add too many custom fields! It can make Bugzilla very difficult to use. Try your best to get along with the default fields, and then if you find that you can't live without custom fields after a few weeks of using Bugzilla, only then should you start your custom fields.

mod_perl Support

Bugzilla 3.0 supports mod_perl, which allows for extremely enhanced page-load performance. mod_perl trades memory usage for performance, allowing near-instantaneous page loads, but using much more memory.If you want to enable mod_perl for your Bugzilla, we recommend a minimum of 1.5GB of RAM, and for a site with heavy traffic, 4GB to 8GB.If performance isn't that critical on your installation, you don't have the memory, or you are running some other web server than Apache, Bugzilla still runs perfectly as a normal CGI application, as well.

Shared Saved Searches

Users can now choose to "share" their saved searches with a certain group. That group will then be able to "subscribe" to those searches, and have them appear in their footer.
If the sharer can "bless" the group he's sharing to, (that is, if he can add users to that group), it's considered that he's a manager of that group, and his queries show up automatically in that group's footer (although they can unsubscribe from any particular search, if they want.)
In order to allow a user to share their queries, they also have to be a member of the group specified in the querysharegroup parameter.
Users can control their shared and subscribed queries from the "Preferences" screen.

Attachments and Flags on New Bugs

You can now add an attachment while you are filing a new bug.
You can also set flags on the bug and on attachments, while filing a new bug.

For more features

To download Bugzilla 3.0 Released (Updated version)