Tuesday, October 12, 2010
Using Retrospectives to Improve Future Testing Efforts
Click here: http://www.softwareplanner.com/guidedtours/edgeui/Camtasia.asp?Filename=UnitingPart05) to begin the presentation. You will learn:
1. What a retrospective is and how it can help your team improve
2. How to conduct a retrospective
3. How to improve future releases by applying what you learn in retrospectives
Friday, September 24, 2010
Software Planner New Release - version 9.4.2
We just issued a new release of Software Planner to production (Release 9.4.2) and it has several new features:
- JIRA Integration – Allows synching of JIRA issues with Software Planner defects. Issues can originate or be updated in either system and will be synced.
Movie: http://www.softwareplanner.com/guidedtours/edgeui/Camtasia.asp?filename=SPJIRAIntegration
User’s Guide: http://www.softwareplanner.com/UsersGuide_swpSyncJIRA.pdf - HP Quick Test Pro (QTP) Integration – Allows automation engineers to run QTP scripts and have the run results appear in Software Planner lists and dashboards.
Movie: http://www.softwareplanner.com/guidedtours/edgeui/Camtasia.asp?filename=SPQTPIntegration_Overview
User’s Guide: http://www.softwareplanner.com/UsersGuide_QTP.pdf - Subversion Integration – Allows automation teams to associate subversion source code with Software Planner requirements, test cases and/or defects.
Movie: http://www.softwareplanner.com/GuidedTours/EdgeUI/Camtasia.asp?FileName=SVNIntegration
User’s Guide: http://www.softwareplanner.com/UsersGuide_SVN.pdf - Microsoft Project Integration – Allows importing and exporting projects from Software Planner to/from Microsoft Project.
Movie: http://www.softwareplanner.com/guidedtours/edgeui/Camtasia.asp?filename=ImportMSProject - Record Locking Feature – Automatically detects if others are editing a record to prevent data collisions.
Movie: http://www.softwareplanner.com/guidedtours/edgeui/Camtasia.asp?filename=RecordLocking
Wednesday, September 8, 2010
Optimizing your Test Efforts during the QA cycle
- How to determine how your QA cycle is progressing
- How to determine your defect resolution rate
- How to use metrics to determine the stability and production readiness of your software release.
You can see the newsletter at: http://www.softwareplanner.com/newsletters/newsletter_2010_09_sp.htm
Monday, August 9, 2010
Uniting your Automated and Manual Testing
http://www.softwareplanner.com/guidedtours/edgeui/camtasia.asp?filename=UnitingPart03
Monday, July 19, 2010
Pragmatic Software is Now SmartBear Software
Pragmatic Software is Now SmartBear Software
You may have heard of the other sister company, the original Smart Bear Software, the peer code review company that created CodeCollaborator. The new SmartBear now includes the old Smart Bear and of course AutomatedQA, which is well known for its TestComplete automated testing and AQtime performance profiling tools. (You may also know that TestComplete works exceptionally well with SoftwarePlanner for test case management).
How will this benefit our users?
For one, our community of users has grown to more than 75,000 software developers and testers with the formation of the new company. We look forward to helping you take advantage of this much larger SmartBear community for expert advice, more support, knowledge sharing and of course improved software quality. Keep an eye out as we start to share tips and tricks, white papers, and other best practices that we hope will help you produce better software.
The combined company is also much better equipped to push product development forward. We are already working on a bunch of new ideas that will not only make it easier for our products to work together, but also put great new functionality in the hands of our users. Stay tuned – you will hear much more from us about automated testing, test management, code review, performance profiling, and development management.
Why did we change our name?
As AutomatedQA, Smart Bear Software and Pragmatic Software worked together to become one company, we had to select a name that we felt reflected our brand values: to be community-focused and offer innovative tools that are highly functional and at the same time actually affordable. Also, now that we have tools that support the immediate needs of both, developers and testers, we needed a name that wasn’t tied to one particular type of product. So we and our sister companies chose the name of one of our very successful existing brands to represent us all going forward. We also think the name is a lot more fun and interesting than using two or three letter acronyms. We hope you like our decision!
Here’s the new logo:
What do you think? Just a few minor adjustments of the original Smart Bear logo, which we thought was pretty cool to begin with as well.
Visit our existing Community page to learn how you can follow us and communicate and share with one another as we continue to add to our products, enhance our web site, and grow our community involvement.
If you want more details regarding the announcement, click here, and stay tuned for some exciting product news in the days and weeks ahead.
Are you curious about all the other tools that are now part of the SmartBear family? Ever needed to increase your test coverage or find those annoying performance issues or memory leaks? Or even find issues before they become bugs through fast and pain-free code review?
Tell your friends, give them a try and check out any of our tools for free:
What’s your take on the New SmartBear? Let us know, leave us a comment, Tweet us or drop us a line.
Friday, July 2, 2010
Best Practices for Planning your Manual Test Effort
Best Practices for Planning your Manual Test Effort
Click on the URL: http://www.softwareplanner.com/guidedtours/edgeui/Camtasia.asp?filename=UnitingPart02 to begin the presentation. You will learn:
1. How to improve the effectiveness of your requirements definition
2. Best practices for creating manual test cases for each requirement
3. How to ensure you have good test coverage for traceability for each requirement
4. How to best organize your manual tests
Friday, June 4, 2010
Best Practices for Planning your Automated Test Effort
Best Practices for Planning your Automated Test Effort
Click on this link (http://www.softwareplanner.com/guidedtours/edgeui/Camtasia.asp?filename=UnitingPart01) to begin the presentation. You will learn:
1. How to identify what test cases should be automated
2. How to best organize your automated test cases
3. How to version and protect your automated test cases
4. How to schedule your automated test cases to run periodically