Powerful Test Metrics
From Software Planner
What are Powerful Metrics?
Metrics are simply a way to measure specific things you are doing, but you could create hundreds of irrelevant metrics that really don’t move you any closer to solving your everyday problems. Powerful metrics are a small set of indicators that are targeted to help you accomplish a specific set of goals.
Metrics Driven by Specific Goals
Before defining your metrics, ask yourself “What goal(s) am I trying to accomplish?”, then write your goals down. For example, typical goals for a tester might be to:
- Ensure that each new feature in the release is fully tested
- Ensure that our release date is realistic
- Ensure that existing features don’t break with the new release
Now that we have our goals defined, let’s figure out how we can create a set of metrics to help us accomplish them.
Selenium testing tool
From IT Spice
Selenium is an open source suite of tools that automate web application testing across many platforms. Basically, in simple words it is a web site testing and automation platform. Considered as a GUI based automation tool, it beckons several browsers on varied platforms. In my opinion, it is a platform, as it can’t really be justified as simple a tool, language, any full application or API, rather regarded as all of these. Selenium actions and accessors are the language you program your scripts in. In addition, Selenium scripts comprise a table constituted with three columns. Amongst them, the first column is the action to perform, second is like the first argument of function and third one is like the second argument in a function.
Lab Automation
From Laboratory Equipment
“Users of lab automation systems will expect more in the future, such as validation or even application-specific and/or custom validations,” says Keith Albert, technical marketing manager at Artel, a manufacturer of automated liquid handling systems. “Proof-of-performance specifications may need to be compared between site acceptance testing and factory acceptance testing.”
Automation systems in the future will also have to be adaptable or flexible enough to move to cell-based assays, and even tissue-based assays, according to CRi’s Hoyt.
Even easier-to-use software systems will be developed, says Hamilton’s Luedke, especially touch-screen interfaces that resemble the Apple iPhone style of interface.
Software testing market
From CIOL
The Global software Testing market is estimated to be $17 billion dollars. The market opportunity for the Indian offshore testing companies is currently $5 billion, estimated to rise to $10 billion in 2010. The software-testing arena would require 25,000-30,000 professional in the next one year as per the IDC report.
Search based software testing call for papers
From cse.unl.edu
Search-based software testing is the use of random or directed search techniques (hill climbing, genetic algorithms etc.) to address problems in the software testing and verification and validation domain. There has been an explosion of activity in the search-based software testing field of late, particularly on test data generation. Recent work has also focused on other aspects such as model-based testing, real-time testing, interaction testing, testing of service-oriented architectures, test case prioritization and generation of whole tests (not only test data).
Researchers and practitioners are invited to submit full papers (10 pages) to the workshop, describing original research, experience or tools. We will also welcome extended abstracts (2 pages) with new results (that may not yet have empirical support), position papers or far-out ideas. Extended abstracts can also be written to describe testing problems for which we can find search-based solutions during the workshop. We will have a poster session where authors of extended abstracts get feedback, but we will also discuss relevant extended abstracts in the main session.
Papers should address a problem in the software testing and/or verification and validation domain and should approach the solution to the problem using a search strategy. Search-based techniques are taken to include (but are not limited to) random search, local search (i.e. hill climbing, simulated annealing etc.), evolutionary algorithms (i.e. genetic algorithms, evolution strategies, genetic programming), ant colony optimization and particle swarm optimization.
Software testing conference
The Third Asia Pacific Software Testing Conference will take place on 25th March, 2010 in Singapore.
The conference tutorials & workshops are scheduled on March 23rd , 24th and 26th, 2010. The conference theme is Software Testing “Innovations & Improvements”.
Papers, presentations and tutorials related to the topics of Software Testing are invited for the conference. The presentation opportunity would be for 35 minutes per speaker for the conference and half day or full day for the tutorials. The following are some of the suggested list of topics. Presenters are welcome to suggest related topics not in the list below.
- Test Concepts & the Testing Process
- Test Methods
- White Box Testing
- Black Box Testing topics such as Functional Testing, Stress Testing, Load Testing, Exploratory Testing, Usability Testing, Recovery Testing, Scenario Testing etc.
- Grey Box Testing
- Test Levels:
- Unit Testing
- Integration Testing
- System Testing
- System Integration Testing
- Regression Testing
- Acceptance Testing
- Non Functional Testing
- Software performance Testing and Load Testing
- Stability Testing
- Usability Testing
- Security Testing
- Internalization and localization
- Destructive Testing
- Testing Process
- Test Measurements
- Test Management
Software Planner CAB
From Softwareplanner
For a company to participate in the Software Planner Client Advisory Board, it must meet these criteria:
- Must be a current Software Planner client in good standing.
- Must be a champion for the product that is willing to offer advice for improvements, help us prioritize features for future releases and be willing to discuss Software Planner with other peers inside your own organisation.
- Must be willing to attend periodic CAB webinars (sometimes monthly, sometimes quarterly) to discuss suggestions for improvement, vote on the priority of suggestions and to help us flesh out feature designs (these meetings will be kept to 1 to 2 hours).
- Must be willing to become a reference for Software Planner (we promise not abuse this privilege).
- Must be willing to participate in our Software Planner discussion forum to offer advice to other Software Planner clients and to learn from others.
Software testing combination at Google
From IT Inform
However, simply looking at the collective whole does not find a lot of problems. At least it doesn’t find a lot of important problems.
Test driving a car is looking at a car holistically. But how often does a test drive find a real bug? A test drive is about look and feel; it’s too high level to be a good bug finding exercise. To find a bug, you hire a mechanic to look at the car, component by component and subsystem by subsystem. Mechanics don’t test by driving the car on a date or by taking a Sunday drive. They test by monitoring specific subsystems and by looking for specific types of problems that eventually work their way out as a bug on a Sunday drive. A mechanic finds flaws quickly in the fuel system, the exhaust system, the electrical system. Sunday drivers must be patient for such flaws to work their way into their line of sight.
Proper software testing requires a combination of Sunday driving and a mechanic’s analysis. It is about looking at the big picture and analysing individual components and capabilities and how they contribute to the collective whole. The way we now do exploratory testing at Google treats it as such.
Back Testing Software
From Artsgrantfinder
Back testing software is an integral cog in the process of analysing trading systems. Back testing is the process of testing a trading strategy using historical data rather than testing it in real time with real money. The metrics obtained from testing via back testing software can be used as an indication of how well the strategy would have performed had it been applied to past trades. Interpreting these results then provides the trader with sufficient metrics to assess the potential of the trading system.
Google testing
From CNN
OK, so it’s a little early in the game to call this one a total fail. But after the breathless anticipation that greeted Google Wave and the hot rush to get an invitation for its beta testing, lots of users found themselves asking, “OK … now what?”
Google, for its part, released an 80-minute tutorial video — leading some observers to argue that if you need an hour and 20 minutes to explain what your product does, you might be in trouble.
It’s designed as a platform to allow users to communicate and collaborate in real time — a tool some predict will be used effectively by developers in the future.
