When writing unit tests for a piece of software, the first decision that needs to be made is the granularity of the test units – if the units are too coarse, there will be a large number of tests for any given unit of code and the result will be hard to manage. If the units are too small, it will be difficult to relate the tests back to the software requirements in any meaningful way.
In order to support both unit testing and general maintenance, any well-designed system should be composed from a set of readily identifiable, cohesive units that individually perform well - defined functions and interact with each other via simple interfaces that hide implementation complexity.
In our case, the existing system was constructed from a set of components that were implemented using the Enterprise JavaBean (EJB) component standard. These components were a logical choice for our unit testing and, consequently, the vast majority of our unit tests were written at the component level.They could easily be verified against system requirements through our software architecture model – a piece of high-level(and lightweight) design that charted the structure and interaction of the components against system requirements.
Despite being an obvious target for unit testing,there were no existing tests in place that we could use, and we encountered a number of challenges when creating new ones. These included:
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.