OWASP Phoronix Test Suite - Linux Testing & Benchmarking Platform Questioning Software evolt.org - Browser Archive 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.
UITest.com TESTAVO Software Testing Zone Software Testing From Wikipedia, the free encyclopedia The Software Testing Portal Software testing is the process used to measure the quality of developed software. Software testing, depending on the testing method employed, can be implemented at any time in the development process. Keyword-driven testing, also known as table-driven testing or action-word testing, is a software testing methodology for automated testing that separates the test creation process into two distinct stages: a Planning Stage, and an Implementation Stage. ...More Exploratory testing: Cem Kaner, who coined the term in 1983, now defines exploratory testing as "a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project." Purge server cache
Evolutionary architecture and emergent design: Test-driven design, Part 1 One of the common agile development practices is TDD. TDD is a style of writing software that uses tests to help you understand the last step of the requirements phase. You write tests before you write the code, solidifying your understanding of what the code needs to do. Most developers think that the primary benefit derived from TDD is the comprehensive set of unit tests you end up with. TDD workflow The important word in the term test-driven development is driven, indicating that testing drives the development process. Figure 1. The workflow in Figure 1 is: Write a failing test.Write code to make it pass.Repeat steps 1 and 2.Along the way, refactor aggressively.When you can't think of any more tests, you must be done. TDD vs. test after Test-driven development insists that the tests appear first. Back to top Perfect numbers To show the design benefits of TDD, I need a problem to solve. To that end, I've chosen perfect numbers. Test after Listing 1. Listing 2. Listing 3. Listing 4.
Evolutionary architecture and emergent design: Test-driven design, Part 2 This is the second part of a two-part article investigating how use of TDD allows better design to emerge from the process of writing tests before you write code. In Part 1, I wrote a version of a perfect-number finder using test-after development (writing the test after writing the code). Then I wrote a version using TDD (writing the tests before the code, allowing the testing to drive the code's design). At the end of Part 1, I found that I had made a fundamental flaw in thinking about the kind of data structure used to keep the list of perfect numbers: my instinct started me with an ArrayList, but I found that the abstraction was more suited to a Set. I'll pick up at that point, expanding the discussion into ways you can improve the quality of your tests and check the quality of the finished code. Test quality The test using the better abstraction of a Set appears in Listing 1: Listing 1. Moist tests My TDD rule of thumb is that tests should be moist but not drenched. Listing 2. Summary