A process seeks to identify and reuse common elements of some particular approach to achieving a task, and to apply those common elements to other, related tasks.Without these common reusable elements,a process will struggle to provide an effective and efficient means of achieving those tasks, and find it difficult to achieve acceptance and use by other practitioners working in that field.Test process is no different; we have many different tasks that need to be achieved to deliver effective and efficient testing,and at a variety of different levels of testing from component/unit/developer testing, through integration/module testing, on into systems testing, and through to acceptance testing. Even before testing process was “invented”, good testers have done things in aparticular way to achieve good results – such as the best way to find the most defects,to complete testing more quickly or more cheaply, to save time by reusing things they had produced in earlier testing projects (such as a template for a test plan or a test script),or to ensure consistent nomenclature (such as common terms for testing phases).
Such enlightened practitioners were even known to share such best practices with their colleagues,passing on or swapping reusable templates,publishing papers on testing techniques,or mentoring other staff on test management approaches,for example.As the IT industry matured,with customers demanding increasingly complex systems,of ever higher quality,in shorter timescales and with lower cost.
The Waterfall Phases and Risk Profile (dotted line).
resulting commercial pressures forced those organizations developing software to seek methods to ensure their software development was as effective and efficientas possible.If they did not find the means to deliver software faster,cheaper,and with better quality,their competitors would.Successive waves of newtechnologies,such as procedural programming,fourth generation languages,and object orientation, all promised to ensure reductions in the occurrence of defects, to accelerate development times,and to reduce the cost of development. Interestingly,it was observed that it was still possible to write poor quality software that failed to achieve its purpose and performed poorly or included defects,no matter what technologies were used!As with so many instances of a new technology failing to solve a particular problem, the issue actually turns out to be a people problem.Human beings need guidance, they need to build upon the knowledge and experiences of others,they need to understand what works and what doesn’t work,and they need to avoid wasting time reinventing things that other practitioners have already successfully produced and used.Project chaos,where each project and practitioner uses different techniques, employs different terminology, or uses (or worse, reinvents from scratch)different documentation,was increasingly considered to be unacceptable. The following sections review a number of the early approaches to software development and testing that sought to avoid such project chaos.
Agile Testing Related Interview Questions
|ETL Testing Interview Questions||Manual Testing Interview Questions|
|Selenium Interview Questions||Database Testing Interview Questions|
|Automation Testing Interview Questions||Software testing Interview Questions|
|Performance Testing Interview Questions||Embedded Testing Interview Questions|
|A/B Testing Interview Questions||Hadoop Testing Interview Questions|
Agile Testing Tutorial
Old-school Development And Testing
Agile Development And Testing
From Waterfall To Evolutionary Development And Test
How To Test A System That Is Never Finished
Implementing An Agile Testing Approach
Agile Testing In A Remote Or Virtual Desktop Environment
Testing A Derivatives Trading System In An Uncooperative Environment
A Mixed Approach To System Development And Testing: Parallel Agile And Waterfall Approach Streams Within A Single Project
Agile Migration And Testing Of A Large-scale Financial System
Agile Testing With Mock Objects: A Cast-based Approach
Agile Testing – Learning From Your Own Mistakes
Agile: The Emperor’s New Test Plan?
The Power Of Continuous Integration Builds And Agile Deve- Lopment
The Payoffs And Perils Of Offshored Agile Projects
The Basic Rules Of Quality And Management Still Apply To Agile
Test-infecting A Development Team
Agile Success Through Test Automation: An Extreme Approach
Talking, Saying, And Listening: Communication In Agile Teams
Very-small-scale Agile Development And Testing Of A Wiki
Agile Special Tactics: Soa Projects
The Agile Test-driven Methodology Experiment
When Is A Scrum Not A Scrum?
Analysis Of The Case Studies
My Agile Process
The Roll-out And Adoption Of My Agile Process
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.