My company is using it in different departments, they are mentioning continuosly the effective way to use in a transversal communication among the different departments.
When your colleagues talk the marvels or a software the least to do is to check on it. Talk with a Software Expert…. Write a Review. For example: Fax and email electronic forms orders, invoices, statements, etc. January 14 C Nitin Bhide 20 January 14 C Nitin Bhide 21 January 14 C Nitin Bhide 24 January 14 C Nitin Bhide 27 January 14 C Nitin Bhide 29 January 14 C Nitin Bhide 34 January 14 C Nitin Bhide 38 Something to shoot for and Be Proud Of.
Total views 3, On Slideshare 0. From embeds 0. Number of embeds Downloads 1. Shares 0. Comments 0. Likes 3. You just clipped your first slide! Clipping is a handy way to collect important slides you want to go back to later.
Now customize the name of a clipboard to store your clips. Visibility Others can see my Clipboard. Cancel Save. Exclusive 60 day trial to the world's largest digital library. Activate your free 60 day trial. Sometimes a cultural change can occur in a subtle manner just by altering the language we use.
Move away from the term "bug" and use "issue" instead to encompass all types of work that should be tracked. The bug system should be tailored to meet the methods that fit the organization the best.
Document the desired workflow. This includes the product components, versions and target release schedules that are known to the development organization. The bug tracking tool should provide meaningful ways to categorize issues against certain components or features. I recommend Bugzilla or Atlassian's Jira for small organizations. Workflow is again the most important item here. Who can open an issue? Does it go straight to development, or to a triage group first?
Can a developer close an issue, or do all issues get resolved and then await QA verification? These are important questions to answer. Infrastructure Document your existing test and development lab infrastructure. This should include a hardware inventory and a diagram of how everything is connected, and why.
Identify gaps where new hardware is required, or hardware isn't being used to its full potential. Then write down how the hardware is used for testing manual and automated. A consisent environment is of utmost importance to successful software testing especially for benchmarking and this includes the lab hardware as well as system configuration. Write a Test Strategy A Test Strategy is a very high level document stating how testing takes place in order to demonstrate product quality.
It should reference the build system, test lab environment, documentation repositories like Wiki or a file server , where results are stored and how the QA team operates. It should state obvious items such as "every feature or component will have a test plan" and "every test plan will be supported by one or more test cases".
Keep this document high level. It needs not be more than a few pages. Write Test Plans A Test Plan is a more granular strategy for a specific feature or product area that is to be tested. It should state methodology for testing, the goals of the testing, required environment and any other information that is important to the technician executing the test. A test plan, however, does not need to contain individual test cases.
Write Test Cases Test cases each document a series of steps used to execute a test, its expected outcome and the final result of Pass or Fail. Many test cases may be required to successfully cover a feature. Test cases typically evolve more quickly than the Test Plan, because with each new bug fix, regression found or feature enhancement, more test cases are added.
Develop or Purchase Tools to Support Test Methodology With a strategy laid out before you that is tailored to your organization, you can make more informed decisions on which tools you need to increase testing efficiency based on your established methodology. Conclusion Improving methodology and process is a never-ending cycle. Having a grip on where you are and where you're going by documenting some of the areas I've mentioned here will allow you to see gaps that may not have been apparent.
Performing this groundwork also lets you know what is already working if it ain't broke, don't fix it! Striving to make smart changes while minimally impacting your development organization builds trust and lessens the natural resistance to change, and that will go a long way towards successful testing and automating strategies.
Comments most welcome! Posted by Derek Douville at PM 38 comments:. One Approach to Automation Frameworks This document is the product of a cursory reflection on my experiences in software development and quality assurance practices.
An Automation Framework is a collection of processes, methodologies, tools and data that will aid in increasing product stability and provide metrics over time. Thus, it is important to make a clear distinction between Test Frameworks strategies and Test Harnesses tools.
In my opinion, an Automation Framework cannot be developed without first evaluating the existing software development practices throughout the organization. The Automation Framework ties everything else together. All too often, the idea of automation is generally viewed as a time and money saver. This is quite to the contrary. The initial ramp-up is demanding, and while the new automation project is underway, manual testing must continue to meet production targets.
The payoff with automation is realized over time; that is, as test cases are automated, the regression suite grows. Eventually, metrics become available to illustrate growth in test coverage and product stability as the development cycle nears code-freeze. By the second iteration, baselines for performance can be integrated, and subsets of the test cases can be moved to a post-build or smoke-screen suite to short-circuit the QA cycle.
Automation places new demands on a QA organization. The availability of a tools framework enables manual testers to elevate their creativity by spending their time trying to break the product in new ways, while the automated regression run takes care of the mundane. Test Automation Developers apply their creativity in a different way: by determining how to automate test cases. Meanwhile, framework tool developers must meet the needs of the automators by providing test execution, analysis, result management and metrics, and treat the framework with as much care as production software.
I believe the best approach to developing something as complex as an automation framework is to evaluate the existing practices and tools in a software development organization, assess the skill levels of various contributors, and take into account project release cycles and deadlines to produce a Requirements Document.
In this way, an organization can transition into a new methodology over time. Some of the requirements include integration of 3rd party tools like Silktest or WinRunner for your UI testing, etc.
As with all automation frameworks, environmental management for test setup and tear-down is a big consideration. Documentation Several departments are required to cooperate to effectively automate. These departments each produce one or more documents to provide enough information to align testing efforts with customer expectations. I will very briefly summarize these here: SRS — Software Requirements Specification: provided by Product Management, this document should present the feature requirements and clearly state the Use Cases for the feature.
ERS — Engineering Requirements Specification: drafted by Engineering to specify the components which must be developed or altered to support the new feature, including database schemas, network protocols, operating systems, etc.
0コメント