background preloader

Open source software testing tools

Open source software testing tools

OWASP Phoronix Test Suite - Linux Testing & Benchmarking Platform Software QA and Testing Resource Center Questioning Software evolt.org - Browser Archive Certifying Software Testers Worldwide - ISTQB® International Software Testing Qualifications Board Google Testing Blog Talks at the 2009 jQuery Conference This past weekend was the 2009 jQuery Conference here in Boston. It was an incredible event – 300 people attended and a ton of discussion, collaboration, and learning happened. Nearly the entire jQuery project team had the opportunity to meet for two days prior to the conference and hash a number of things out – figuring out most of the planning for the upcoming year. (Left to Right: Mike Hostetler (Infrastructure), John Resig (Core), Paul Bakaus (UI), Brandon Aaron (Core), Richard D. A full list of the presentations that were given can be found on the events site. Recent Changes to jQuery’s Internals A run-down of all the features and internal changes made in 1.3, 1.3.1, 1.3.2, and 1.3.3/1.4. Understanding JavaScript Testing A broad overview of all the different testing solutions that exist for JavaScript and where they might best fit into your full testing solution. State of jQuery ’09 A quick overview of the past year of jQuery and a look towards the upcoming year. Comments are closed.

Software testing Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test.[1] Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include the process of executing a program or application with the intent of finding software bugs (errors or other defects), and verifying that the software product is fit for use. Software testing involves the execution of a software component or system component to evaluate one or more properties of interest. In general, these properties indicate the extent to which the component or system under test: As the number of possible tests for even simple software components is practically infinite, all software testing uses some strategy to select tests that are feasible for the available time and resources. Overview[edit] Defects and failures[edit]

UITest.com Oh, shit, git! TESTAVO

Related: