CSTE Certification

Certified Software Tester (CSTE) Certification

2015-01-08T18:05:00.000+05:30

Certified Software Tester (CSTE)

CSTE testing certification is the basic certification to check testers skill and understanding of software testing theory and software testing practices.

The CSTE program was developed by leading software testers as a means of recognizing software testers who demonstrate a predefined level of testing competency. The CSTE program is directed by an independent Certification Board and administered by the Quality Assurance Institute. The CSTE program was developed to provide value to the profession, the individual, the employer, and co-workers.

Common Body of Knowledge (CBOK)-

The Certification Board defines the skills upon which software testing certification is based. The current CBOK includes these skill categories:

1) Test Principles;
2) Test Planning;
3) Test Management;
4) Building a Test Environment;
5) Risk Analysis;
6) Text Execution;
7) Test Design;
8) Defect Tracking;
9) Acceptance Testing; and
10) Test Analysis and Reporting.

Examination Process to Evaluate Competency-

The successful candidate must pass a four-part examination (based on the CBOK) with a grade of 75%, or greater, on each part. Only 31% of the prequalified applicants pass the examination the first time, making this a prestigious certification to obtain.

Here are some important links that would be handy to all aspirants:
(I have collected these at one location as I found them)

1. Main website for Certified Software Tester (CSTE)

2. CSTE software testing certification exam question pattern

3. Check your eligibility for CSTE certification
(Take this sample CSTE examination)

4. Learning resource

5. Resources for Professional s/w testers (Bret Pettichord)

6. CSTE CBOK V6.2

7. V-Model of software testing

8. CSTE Certification Mock Test
(Test has 50 Multiple Choice Question with only ONE answer
To pass you need 38 marks)

9. CSQA V6.2 CBOK [this is not required but just in case anyone wants]

Lets see more (as given in the official website) about CSTE certification:

Checking Prerequisites:

To qualify for candidacy, each applicant must meet one of four prerequisites:

A 4 year degree from an accredited college-level institution and 2 years experience in the information services field
A 3 year degree from an accredited college-level institution and 3 years experience in the information services field
A 2 year degree from an accredited college-level institution and 4 years experience in the information services field
6 years experience in the information services field

AND

Are working, or have worked at any time within the prior 18 months, in the field within covered by the certification designation

Depending upon a compliance sample selected according to program criteria, the applicant may be required to provide detailed education and/or employment documentation supporting the prerequisite option selected on the application. If selected for verification, the applicant must supply the documentation to the program. Applicants who fail to provide the requested documentation will not be allowed to sit for the exam or, if the exam has been taken and passed, may be subject to de-certification.

If you want to apply for the examination:
A. A completed Certification Candidacy Application must be submitted through the Customer Portal for entrance to Software Certifications as a candidate for any particular certification. It should be submitted by individuals who:

Are working, or have worked at any time within the prior 18 months, in the field covered by the certification designation
Have significant experience and breadth of knowledge to have mastered the basics of the entire Software Testing Common Body of Knowledge
Have reviewed the Software Testing Common Body of Knowledge

The Application Fee options are:

$350.00 ~ (Fees to be paid in US Dollars - see Payment Policy). Fees includes CBOK (PDF) & Initial Exam. OR
$420.00 ~ (Fees to be paid in US Dollars - see Payment Policy). Fees includes CBOK (PDF, Book, and CD) & Initial Exam

How will certification help me?

* In today's compititive IT industry there is a need for you to stand out in the crowd, to get distinguished from others. By doing the certification you are telling the management & world that your expertise is now recognized and you are serious about your profession. It gives confidence to others that you can now lead and demonstrate a level of understanding in carrying out assignments according to industry principles and practices.

* You get recognized by business and professional associates as a PROFESSIONAL

* The certifications will lead you to career advancement and will help you lead at your job better in a way that you can never imagine.

* Studies show that Certified professionals get higher salaries and its easy to get better jobs as compared to Non certified professionals

Unix Tutorials, Linux Tutorials

2013-07-19T01:48:00.001+05:30

Very Simple Unix Commands
VERY basic UNIX tutorial - This guide is Intended for people with pretty much zero knowledge of Unix.

Webteacher Beginning Tutorial - This is a CGI tutorial. They say: This tutorial will walk you through the basics of creating CGIs with Perl on a Unix platform. Unlike other tutorials I've read, this does not assume you know anything about CGIs, Perl, or Unix.
Intro to UNIX - This is an old page, but will get you started with Unix.
A nice Unix tutorial for beginners
UNIXhelp for Users - Starts with very basic stuff and moves on to more detailed topics.
Web Reference UNIX Tutorial - This is a Fourteen section tutorial, each of which addresses a fundamental aspect of UNIX computing.
A Comprehensive Guide to FreeBSD - They say this is: An Absolute Beginners Guide to FreeBSD. This section gives an overview of what FreeBSD is, and how to utilize resources for obtaining more information about FreeBSD.

Unix System Administrator

Unix System Security - This is a several part overview of how to secure your Unix system.
Tutorials on various utilities Unix System Administrators use - This is the DreeBSD documentation page. You will be able to find a great deal of information here.
Tutorials on Solaris/SunOS Modems and Terminals also UNIX Sysadmin Resources
Samba Administrator's Handbook
Getting Samba to work is challenging -- this book helps.

API testing solution - Agile Quality eBook

2013-03-27T08:26:00.003+05:30

Agile Quality eBook

Increase Velocity while Controlling Defects

This 12-page eBook aggregates 10 hands-on tips for ensuring that each new feature is truly "done" according to stakeholder expectations... and free of the defects that commonly derail Agile projects.
Development managers and scrum masters can deliver better software faster by learning how to extend Agile quality practices to:

Bake quality into the code without disrupting developers' workflow

Know when code changes impact behavior that your TDD and functional tests don't cover

Enable developers to test specific parts of complex systems...without tedious setup

Enable QA to perform end-to-end testing...even if some components incomplete or unavailable

Pinpoint exactly which test cases need to be rerun after an application update

Download your copy here:

Resilient Willpower Mind Map

2013-03-16T06:07:00.000+05:30

More CSTE practice

2013-03-12T06:56:00.001+05:30

CSTE exam questions

CSTE Add-on Exercise 1

CSTE Exercise Exam 1

CSTE Certification Process

CSTE Mock Test 2

Quetions related to CSTE

CSTE Certification Preparation Guide

CSQA Skills 3

CSTE Dumps That are Worth Buying 3

CSTE Certification CBOK 2

CSTE 2009 Questions 2

CSTE Certification : Study Manual (77pages) 3

2006_CSTE Sample Exam1 2

CSTE mock test paper 3

CSTE-PracticeExam2 1

CSTE- PracticeExam1 3

CSTE QUESTIONS

CSTE Objective Questions 3

Software Certifications in QA 2

Certified Software Tester (CSTE) certification 1

CSTE BOOK 1

CSTE CBOK 1

certifications preparation mock ups

CSQA book

CSTE model questions

CSTE- Common body of knowledge 1

CSQA Knowledge Domain 3

CSTE Sample Paper 4.doc

CSTE Sample Paper 2.doc

CSTE Sample Paper 1.doc

CSTE complete question and answer -Latest

CSTE Certification CBOK 2

Software Engineering : software testing

CERTIIFIIED MANAGER off SOFTWARE TESTIING 1

Certified Software Tester 1

CBOK 1

common body of knowledge 2

CSTE sample paper 2

Sample paper for cste 1

Cover Letter Samples

2013-02-26T06:45:00.005+05:30

Cover Letter Samples

Nonprofit Correspondence Samples

See sample cover letters and thank-you notes that are appropriate to send to nonprofit employers.

Sales Cover Letter Sample

Not sure how to sell yourself for the job? Check out this sample cover letter for a sales job.

Sample Cover Letter for an Elementary School Teacher

Could your cover-letter writing skills use some extra help? If so, get ideas from this sample cover letter for an elementary school teacher.

Sample Cover Letter

Stumped on how to write a cover letter that will catch an employer's attention? Get ideas from this sample.

Sample Cover Letter for an IT Professional

You don't want your cover letter to read like the code you write. Get some inspiration from this sample cover letter.

Sample Cover Letter for an Unemployed Job Seeker

Your cover letter can address your unemployment situation while still playing up your experience and accomplishments. Get some ideas from this sample.

Sample Letter of Recommendation

Ever wanted to write a glowing letter of recommendation but weren't sure what it should look like? Here's an example.

Mid-Career Cover Letter Sample

Cover letters should vary depending on the opportunity and your experience, but this example will get you started.

Sample Cover Letter for a Pharmacy Technician

Going for a job as a pharmacy technician? Be sure to use your cover letter to convey your experience and training. Get ideas from this sample.

Sample Cover Letter for an Investment Banker

This sample cover letter for an investment banker conveys the candidate's qualifications and achievements.

2013-02-26T06:45:00.001+05:30

Sample Resumes by Industry

Want to be the standout job candidate in your field? Then writing a resume that highlights your industry-specific experience, accomplishments and credentials is essential. If you need help customizing your resume to your field, check out these examples of resumes for various careers and career levels in the following industries:

Administrative/Support

Art/Design/Media

Automotive

Education

Engineering

Finance/Accounting

Healthcare

Human Resources

Insurance

Law Enforcement

Manufacturing

Marketing/PR

Nursing

Real Estate

Restaurant & Hospitality

Retail

Sales

Science

Technology

Trades

Transportation & Warehousing

Step-by-Step Guide to Negotiating a Great Salary

2013-02-26T06:43:00.003+05:30

Step-by-Step Guide to Negotiating a Great Salary

By Kim Lankford, Monster Contributing Writer

Here's a secret: Employers rarely make their best offer first, and job candidates who negotiate generally earn much more than those who don't. And a well-thought-out negotiation makes you look like a stronger candidate -- and employee.
"We found that those people who attempted to negotiate their salary in a constructive way are perceived as more favorable than those who didn't negotiate at all, because they were demonstrating the skills the company wanted to hire them for," says Robin Pinkley, coauthor of Get Paid What You're Worth and an associate professor of strategy and entrepreneurship at Southern Methodist University's Cox School of Business.
You can start laying the groundwork for your salary negotiation even before the first interview. Here's a step-by-step guide:
During the Interview Process

Do Your Research: Before the interview, learn about the company's salary ranges and benefits as well as industry salary ranges. Also learn about the company, its competition and the industry. Then think about what you want from the job, both in terms of salary and benefits, as well as opportunity and upward mobility, Pinkley says. This information will become valuable during the interview and salary negotiation.

Don't Talk Turkey Too Early: "You never win by talking about money early on," says Lee Miller, author of Up: Influence, Power and the U Perspective -- The Art of Getting What You Want. "The time to talk about money is when they've fallen in love with you." Before that, you're just one of many easily dismissed candidates. But once the employer has decided you're right for the job, "it becomes an issue of, ‘how are we going to make this happen?'" Miller says.

Avoid the Salary Requirements Trap: Pinkley tells people to say: "I completely understand why this is an important issue -- you're trying to determine who you want to continue in this process, and it doesn't make much sense to pursue candidates you aren't going to get. Secondly, I know that the tendency is for people to lowball their salary range, because they don't want to get out of the pool. My preference is to figure out, independent of these issues, the degree to which there is a good fit here and the extent to which I can bring value to this organization and the extent to which I'm going to be fulfilled and involved and committed to this position. I suggest we wait to have the salary conversation until you're prepared to make an offer."
If they still want a number, leverage your research to talk industry-standard ranges, not specific numbers.

At Time of Offer

Strike First: Try to mention a specific salary before the employer does. This will start the negotiations in your ballpark. "The whole negotiation is based on that first offer," Pinkley says.
Don't Commit Too Quickly: The employer often offers the job and salary simultaneously. Never say yes right away -- even if you like the offer. "I would always come back and try to get more," Pinkley says. Tell them you'll give them an answer within a certain time frame.
Make Them Jealous: If you've been interviewing for other jobs, call those prospective employers, tell them about your offer, and see if they can speed up the interview process -- or make you an offer. Knowing you have another offer will make you more attractive to them.
When it's time to answer the first employer, mention the other employers' interest to help boost your value. But don't make up offers. It's easy to check, and the interest alone will help you look good.
Articulate Your Expectations: Tell the employer what you want from the job, in terms of salary, benefits and opportunity. "It may be time off, flexibility about where you work, autonomy or ownership over a particular area, it may be your title -- whatever has a perceived value to you," says Joyce Gioia, president of the Herman Group, a think tank of management consultants and futurists.
Negotiate Extras: If the employer can't offer you the salary you want, think about other valuable options that might not cost as much. Miller always recommends asking for education, which can make a big difference in your long-term marketability.
Quantify Your Value and Performance: Mention your value in quantifiable terms, such as how much money you saved your company and how your projects increased revenues by X thousands of dollars, Gioia says. Then tell them specifically how valuable you expect to be in your new job.

You also can add a few contingencies showing your confidence in your performance. You could ask the employer to give you a salary review after six months rather than a year or for a year-end bonus if you make a certain amount of money. "It shows that you believe in yourself and are committed to bringing what you say you can do," Pinkley says. "You believe you are going to bring significant value to the organization.

Important links for websites and blogs!!

2013-02-09T08:37:00.002+05:30

#	Site Web Link	Author
1	James Bach's Blog	James Bach
2	Testing at the Edge of Chaos	Matt Heusser
3	Agile Testing	Grig Gheorghiu
4	Martinfowler.com	Martin Fowler
5	Tester Tested!	Pradeep Soundararajan
6	Testing Blog	Google Testing
7	Cem Kaner’s Blog	Cem Kaner
8	Miško Hevery	Miško Hevery
9	DevelopSense	Michael Bolton
10	Sara Ford's Weblog	Sara Ford
11	Steve Rowe's Blog	Steve Rowe
12	Test Obsessed	Elisabeth Hendrickson
13	Software Quality Insights	( various )
14	Exploration Through Example	Brian Marick
15	Gojko Adzic	Gojko Adzic
16	Thinking Tester	Shrini Kulkarni
17	Chris McMahon's Blog	Chris McMahon
18	JW on Test	James Whittaker
19	Software testing help	Vijay
20	Corey Goldberg	Corey Goldberg
21	Quality Frog	Ben Simo
22	Testing Hotlist Update	Bret Pettichord
23	Abakas	Catherine Powell
24	Collaborative Software Testing	Jonathan Kohl
25	Sbarber's blog	Scott Barber
26	Adam goucher	Adam goucher
27	Eric Jarvi	Eric Jarvi
28	Karen N. Johnson's blog	Karen N. Johnson
29	Test Guide	Michael Hunter
30	Curious Tester	Parimala Shankaraiah
31	Testy Redhead	Lanette Creamer
32	Antony Marcano's blog	Antony Marcano
33	All Things Quality	Joe Strazzere
34	I. M. Testy	Bj Rollinson
35	Software testing zone	Debasis Pradhan
36	PractiTest QA Blog	Joel Montvelisky
37	Practical QA	Linda Wilkinson
38	Marlena’s Blog	Marlena Compton
39	Software Testing and more	Ewald Roodenrijs, Andréas Prins
40	patrickwilsonwelsh.com	Patrick Wilson-Welsh
41	Quality Assurance and Software Testing	( various )
42	Testing Testing 1,2,3	Chan Chaiyochlarb
43	Mike Kelly's blog	Mike Kelly
44	Test this Blog	Eric Jacobson
45	Enjoy testing	Ajay Balamurugadas
46	Evil Tester	Alan Richardson
47	Tooth of the Weasel	Alan Page
48	Charlie Audritsh's blog	Charlie Audritsh
49	Maverick Tester	Anne-Marie Charrett
50	Paul Gerrard's blog	Paul Gerrard
51	shino.de	Markus Gaertner
52	Cartoon Tester	Andy Glover
53	cLabs Blogki	Chris Morris
54	Jeff Fry on Testing	Jeff Fry
55	Venkat's Blog	Venkat Reddy Chintalapudi
56	Agile Testing and Process Thoughts	Janet Gregory
57	Software Testing Stuff	( various )
58	selenadelesie.com	Selena Delesie
59	Software Sleuthing	Josh Poley
60	The Software Quality Blog	Vijay Bhaskar
61	Expected Results	Phil Kirkham
62	One of the wolves	Tim Coulter
63	Musing about Software Testing	Keith Stobie
64	Jon Bach's blog	Jonathan Bach
65	Quardev	( various )
66	Software Testing Club Blog	( various )
67	TestToTester	Sharath Byregowda
68	Agile Testing with Lisa Crispin	Lisa Crispin
69	Confessions of a Passionate Tester	Dawn Cannan
70	I am filled with solutions	Dustin Andrews
71	Software Tasting	Geordie Keitt
72	Rosie Land	Rosie Sherry
73	Still Life	Steve Swanson
74	Brian Osman	Brian Osman
75	Dhanasekar S’s Blog	Dhanasekar S
76	The Social Tester	Rob Lambert
77	QA Insight	Brent Strange
78	The Testing Blog	( various )
79	Testingminded	Steven Machtelinckx
80	John McConda's blog	John McConda
81	Software Testing	Len DiMaggio
82	Jeroen's world of Software Testing	Jeroen Rosink
83	TestingPerspective	Rahul Verma
84	Adam White	Adam White
85	Purple Box Testing	Trish Khoo
86	Lessons Learned by a Software Tester	Paul Carvalho
87	Pliant Alliance	Tim Beck
88	Testjutsu	Ben Kelly
89	Illiteration	Jared Quinert
90	Tester Testifies	Raj Kamal
91	Santhosh Tuppad's Blog	Santhosh Tuppad
92	Teknologika	Bruce McLeod
93	Creative Tester	Anuj Magazine
94	Tester Troubles	Ray Claridge
95	Thoughts on QA and Engineering	John Overbaugh
96	Quick Testing Tips	( various )
97	Cruisin QA	Brett Leonard
98	QA Hates You	The Director
99	Tester Lost Focus	Michelle Smith
100	James McCaffrey's blog	James McCaffrey

101 Brett Pettichord Brett Pettichord

Google: Android has security flaw

2013-02-09T07:42:00.004+05:30

A security flaw has made it easy for scam artists to send phony text messages to Android phones with help of a security flaw, a report has said.

In late October, researchers at North Carolina State University alerted Google to a practice called "smishing" that can ensnare consumers in fraud.

Google's security officials confirmed the flaw and promising to correct it.

Within days they had incorporated a fix into the latest version of the Android operating system, Jelly Bean 4.2, and made available a security update for earlier versions.

But for most Android phones, the fix never arrived, and for many, it never will, the Washington Post reports.

That is because it is not clear which company, Google, the smartphone maker or the wireless carrier that sells it, bears ultimate responsibility for the costly process of getting security updates to an Android device.

According to the paper, fixes to known security flaws can take many months to reach individual smartphones, if they arrive at all.

Security experts said that the problem has contributed to making the world's most popular mobile operating system more vulnerable than its rivals to hackers, scam artists and a growing universe of malicious software.

Breaches remain more common on traditional computers than on smartphones, which have been engineered to include security features not found on desktop or laptop machines, experts added.

The report pointed out that if there was a major outbreak of malicious software, the fractured nature of the system for delivering updates could dramatically slow efforts to protect information carried on Android phones, including documents, passwords, contact lists, pictures, videos, location data and credit card numbers.

source

Myths and Facts about Software Testing...

2013-02-01T07:13:00.000+05:30

- Software Testing can not show the absence of errors

- There is no last bug in the software / application

- Maximum coverage through minimum test cases is a big challenge of testing.

- Even for simple program of loops, there can be over million paths – testable manually in million years. Domain of possible inputs is too large to test. Also, there are too many possible paths to test the program. Even if, theoretically speaking, one could design excellent test cases to detect all defects, does one have the luxury of time and resources to do so in practice?

- Preventive testing is very important. Verify documents, design, code at each stage of development to prevent errors from getting in. Use a variety of techniques for this. Code review itself throughs up many defects that may be too difficult to detect by execution of tests. On the other hand, test execution can detect errors that can not be easily detected by code reviews. Therefore, various techniques are complimentary in nature and it is only through their combined use that one can hope to detect most errors.

- Even though development tends to be given more importance than testing. A good test design is perhaps intellectually more challenging than the software design and development. Given reasonable practical limits to the quality of test design in practice, it is easy to understand that why it is difficult to uncover all defects through testing.

Source

Software Testing Myths & Facts

There are certain popular myths about the testing discipline which are deep rooted in the software development community. Over the years, with several major products shipped on time, with high quality helping keep the software maintenance costs within predicted and manageable numbers are helping shatter these myths.

Testing Myths & Facts
Herein we list some of those myths we’ve heard time and again and the facts associated with them that we really believe in:

Myth: Initiating testing activities earlier in the development cycle increases delivery time while reducing the number of features in the product.
Reality: Testing is not the time-consuming activity in a development lifecycle. Diagnosing and fixing defects are the time-consuming, bottleneck activities.

Myth: You can't test if you don't have a product to test.
Reality: Iterative testing isn't limited to testing code.

Myth: Continually regressing everything every time we change code is tedious and time consuming…but, in an ideal world, it should be done.
Reality: Regression testing doesn't mean "testing everything, every time."
Iterative regression testing means testing what makes sense in each phase and iteration. It also means modifying our coverage based on the impact of the change, the history of the product, and the previous test results.

Myth: It's not a bug -- the feature is working as designed.
Reality:The over-explanation of why the product is doing what it's doing is a common trap. Sometimes we just know too much. When defects are triaged and reviewed, we often explain away the reasons for the defect. Sometimes we tag defects as "works as designed" or "no plans to fix" because the application is actually working as it was designed, and it would be too costly or risky to make the design change. Similarly, we explain many usability concerns as "it's an external component" or "it's a bell and whistle." Our widgets or UI controls may have known limitations. Or we may even tell ourselves that "once the user learns to do it this way, they'll be fine."

Myth: A tester's only task is to find bugs.
Reality: This view of the tester's role is very limited and adds no value for the customer. Testers are experts with the system, application, or product under test. Unlike the developers, who are responsible for a specific function or component, the tester understands how the system works as a whole to accomplish customer goals. Testers understand the value added by the product, the impact of the environment on the product's efficiency, and the best ways to get the most out of the product.

Myth: We don't have enough resources or time to fully test the product.
Reality: You don't need to fully test the product -- you need to test the product sufficiently to reduce the risk that a customer will be negatively affected.

Myth: Testing should take place in a controlled environment.
Reality: The more the test environment resembles the final production environment, the more reliable the testing. If the customer's environment is very controlled, then you can do all your testing in a controlled environment. But if the final production environment is not controlled, then conducting 100 percent of your testing in a controlled environment will cause you to miss some important test cases.

source

Web Application check lists

2013-01-29T05:48:00.003+05:30

Web Application Security Check List1

OWASP Testing Checklist

e-Books on Software Testing

2013-01-21T09:40:00.000+05:30

e-Books on Software Testing

Web Services Testing with soapUI

Selenium 2 Testing Tools

Continuous Testing

Integrating PHP Projects with Jenkins

Building and Testing with Gradle

Design Driven Testing

The Art of Application Performance Testing

Web Security Testing Cookbook

Pragmatic Unit Testing in Java with JUnit

Pragmatic Unit Testing in C# with NUnit (2nd edition)

Scripted GUI Testing with Ruby

Test Driven Development for Embedded C

Test Driven

Learning Oracle PL/SQL [online manual]

Oracle Ships Critical Security Update for Java

2013-01-16T09:24:00.000+05:30

has released a software update to fix a critical security vulnerability in its Java software that miscreants and malware have been exploiting to break into vulnerable computers.

javanix2Java 7 Update 11 fixes a critical flaw (CVE-2013-0422) in Java 7 Update 10 and earlier versions of Java 7. The update is available via Oracle’s Web site, or can be downloaded from with Java via the Java Control Panel. Existing users should be able to update by visiting the Windows Control Panel and clicking the Java icon, or by searching for “Java” and clicking the “Update Now” button from the Update tab.

This update also changes the way Java handles Web applications. According to Oracle’s advisory: “The default security level for Java applets and web start applications has been increased from “Medium” to “High”. This affects the conditions under which unsigned (sandboxed) Java web applications can run. Previously, as long as you had the latest secure Java release installed applets and web start applications would continue to run as always. With the “High” setting the user is always warned before any unsigned application is run to prevent silent exploitation.”

It’s nice that Oracle fixed this vulnerability so quickly, but I’ll continue to advise readers to junk this program altogether unless they have a specific need for it. For one thing, Oracle tried (and failed) to fix this flaw in an earlier update. Also, it seems malware writers are constantly finding new zero-day vulnerabilities in Java, and I would not be surprised to see this zero-day situation repeat itself in a month or so. Also, most users who have Java installed can get by just fine without it (businesses often have mission-critical operations that rely on Java).If you need Java for a specific Web site, consider adopting a two-browser approach. If you normally browse the Web with Firefox, for example, consider disabling the Java plugin in Firefox, and then using an alternative browser (Chrome, IE9, Safari, etc.) with Java enabled to browse only the site(s) that require(s) it.

Entry Guide to Software Testing

2012-12-10T05:34:00.005+05:30

Product Description: This ebook is designed for the aspirants who are interested in getting into the Software Quality Assurance (QA) jobs. The contents put together in this ebook are systematically organized so that the reader can begin as a novice with no prior knowledge of Software QA process and will lead into the details of the QA responsibilities, explaining each topic in an easy to understand format.

Buy it now!!

File Format: The ebook is the pdf format and you will need to download Acrobat Reader to read this ebook. You will also need Winzip or 7-Zip (free download available) to open this ebook. Product Delivery: Product will be available for download immediately once the payment has been successfully processed. You will have to save the ebook to your computer.

Buy the book now!!

or Click here to review and buy at special price

Jacqueline Kennedy by Caroline Kennedy - Books

Automating Software Testing Using Program Analysis

2012-12-09T06:41:00.001+05:30

I was thrilled by this post guys over Automating Software Testing Using Program Analysis!! It's superb!! I would really want people to read this.. especially those who are into automated software testing....

During the last decade, code inspection for standard programming errors has
largely been automated with static code analysis. Commercial static program analysis tools are now routinely used in many software development organizations.

These tools are popular because they find many software bugs, thanks to
three main ingredients: they’re automatic, they’re scalable, and they check many properties.
Intuitively, any tool that can automatically check millions of lines of code against hundreds of coding rules is bound to find on average, say, one bug every thousand lines of code.

Three new tools combine techniques from static program analysis, dynamic analysis, model checking, and automated constraint solving to automate test generation in varied application domains.

Read on more...

Please download PDF from this link (1.03 MB)

Source of this article

SQA resource

2012-12-08T08:04:00.002+05:30

Bugs and Fixes what is testing, bug reports, impact...	Software Life Cycle Software Product Life Cycle Chart...
Bugs Life why are there bugs, bug stories...	SQA Career watch your career take off...
Bug Tracking price comparison of bug tracking systems...	Testers Area get your professional page here ...
Companies and Products companies, products, services...	Tester to Tester discussions, exchange ideas...
Documentation and Strategy test plan, cases, check list, examples...	Testing Center practice QA...
Methodology and Techniques test reviews in alphabetical order	Testing Newsletter news, announcements...
More Resources software testing related sites...	Testing Tips black and white box tips, automation...
Publication and News industry news, seminars, conferences...	Tools and Automation tools, product information...
QA Team leadership within SQA team...	Tutorials and Training teach yourself...

Source

PL SQL Test Set

2012-12-08T08:02:00.002+05:30

Quiz Sets

PL SQL Mock Test Set-1

PL SQL Mock Test Set-2

Software Project Estimation - Test Effort Estimation Using Use Case Points

2012-12-08T08:01:00.001+05:30

Test Effort Estimation Using Use Case Points

By: Suresh Nageswaran
Cognizant Technology Solutions,
National Games Road,
Yerwada, Pune – 411006.
Maharashtra, India
(+91-020) 669 19 60

This paper presents a new approach to the estimation of software testing efforts based on Use Case Points [UCP] as a fundamental project estimation measure. From preliminary applications on our web-based projects, we conjecture that this could in fact be more reliable than FP. The caveat here is that the Vmodel must be in use and use case generation must start becoming available right at the requirements gathering phase. The acceptance test plan is then prepared with the use cases from the requirement documents as input.
Further work could provide a more exact relationship between the two.

Download free from by clicking on this link

Selenium Test Set

2012-12-08T07:54:00.000+05:30

Quiz Sets

Selenium Professional Test Set-1

Selenium Professional Test Set-2

Selenium Professional Test Set-3

Source

Software Testing Test Set

2012-12-08T07:49:00.001+05:30

Quiz Sets

Software Testing Mock Test Set-1

Software Testing Mock Test Set-2

Software Testing Mock Test Set-3

Software Testing Mock Test Set-4

Software Testing Mock Test Set-5

Software Testing Mock Test Set-6

Software Testing Mock Test Set-7

Software Testing Mock Test Set-8

Software Testing Mock Test Set-9

Software Testing Mock Test Set-10

Software Testing Mock Test Set-11

Software Testing Mock Test Set-12

Software Testing Mock Test Set-13

Software Testing Mock Test Set-14

Software Testing Mock Test Set-15

Source

Software quality assurance or SQA and difference with Quality check and Software Testing

2012-12-08T07:47:00.000+05:30

Quality:

Quality means consistently meeting user requirements in terms of cost , delivery schedule & service.

Quality Assurance (QA):

- QA is planned and systematic way to evaluate quality of process used to produce a quality product.

- The goal of a QA is to provide assurance that a product is meeting customer’s quality expectations.

- QA deals with how to prevent bugs from occurring in a product being developed.

- Software Quality Assurance Engineer’s main responsibility is to create and implement methods and standards to improve development process.

- QA is associated with activities like measuring the quality of process used to develop a product, process improvement and defect prevention.

- It consists of auditing and reporting procedures related to development and testing.

Quality Control (QC):

Quality control name comes from manufacturing industry where QC inspector evaluate sample products taken from the manufacturing line, test them & if the products fail the test they have the authority to shut down the whole production line.

- QC in software industry is evaluating software product, find the defects & suggest improvements.

- QC implements the process established by QA.

- Software tester is responsible for QC.

- If required, personnel involve in QC have to carry out QA tasks as well.

Software Testing:

- Software testing is a planned process that is used to identify the correctness, completeness, security and quality of software.

- Testing is generally done to demonstrate that the software is doing what it is supposed to do as well as the software is not doing what it is not supposed to do.

- The goal of testing or software tester is to locate defects and make sure that they get fixed.

These are the basic differences between the three concepts. Sometimes there is an overlap of duties between tester, QA Engineer and QC Engineer. As per the need, some testers might be required to perform certain QA activities & some QA-ers perform testing of product.

Software Quality Assurance Plan

2012-12-08T07:45:00.001+05:30

Software Quality Assurance Plan (SQAP) is to define the techniques, procedures, and methodologies that will be used at the Center for Space Research (CSR) to assure timely delivery of the software that meets specified requirements within project resources.

The use of this plan will help assure the following:
(1) That software development, evaluation and acceptance standards are developed, documented and followed.
(2) That the results of software quality reviews and audits will be given to appropriate management within CSR. This provides feedback as to how well the development effort is conforming to various CSR
development standards.
(3) That test results adhere to acceptance standards.

Following is a Software Quality Assurance Plan submitted by:

Center for Space Research
Massachusetts Institute of Technology
Cambridge, MA 02139

csr_sqa_plan.pdf (96.9 MB)

Database Testing Tutorials

2012-12-08T07:20:00.001+05:30

Database testing/Back-end testing is very important.

I have summarized a set of tutorials that could be handy fr testers.

If there is any bug in the database that bug may cause a severe problems like – dead-locking, data corruption, poor performance etc. These bugs are very difficult to find in manual testing / front-end testing.

So for all-rounder testers, knowledge of Database testing/SQL testing / Backend testing is very important.

Below are some free Database testing tutorials, through which you will learn about the following:

1. Why DB testing is important?
2. How DB testing is carried out?
3. SQL queries

Tutorial Database Testing using SQL - Part1

SQL For Testers – Part 2

SQL interview questions for Testers

Source

Quality Engineered Software and Testing (QUEST) Conference

2012-11-15T09:16:00.000+05:30

Join the QUEST for Quality Engineered Software and Testing!

In today’s fast paced environment, you have limited time and budget for training. But you still need to remain current in your profession and find solutions to your most pressing challenges. Your want to learn from the industry thought leaders, but you also want to know what other companies are doing. You want to connect with other practitioners like yourself. You want to learn about today’s products and services from vendors, but you don’t want to feel pressured to buy. This is what QUEST is all about.

Whether you join QUEST online or attend the annual QUEST conference in-person, you'll have the opportunity to LEARN, ACCESS, APPLY, and CONNECT -- the mission of QUEST.

JOIN NOW