THE GATE TO THE REAL SOFTWARE TESTING EXPERIENCE AND KNOWLEDGE IN "TESTING A SOFTWARE" WORLD

Saturday, December 17, 2011

Risk Based Testing

Risk Based TestingRisk Based Testing is a method for prioritizing the tests based on the risk of their failure because tester cannot test everything within available resource. To use Risk Based Testing, we normally use following factor to prioritize tests: - Usage frequency. - Cost of failure. - Impact module from change. We should work closely with business and developer to get this information. We should do other testing techniques (e.g., black box testing technique, automation, regression testing) to optimize the cost of testing as the supplementary...

Monday, December 12, 2011

Tips to improve technical knowledge for tester in Agile Testing

Tips to improve technical knowledge for tester in Agile TestingIt is important for tester who participates in Agile Testing to improve technical knowledge. This knowledge is essential for discussing with developer. So, I summarize the key things that I normally use for improving my technical knowledge. Tips to improve technical knowledge1. Learn the technology and architecture of our software First of all, we should understand which technology is used for implementing our application and what it is. Then, we should understand the high-level architecture....

Thursday, December 8, 2011

What is Regression Testing? Why should we use Regression Testing?

What is Regression Testing? Why should we use Regression Testing?What is Regression Testing?Regression Testing is software testing activity that is used to ensure that existing functionality has no impact from change in a system, such as functional enhancements, patches or configuration/environment changes. Regression Testing is activity that rerun previously run tests (Existing functionality) and check whether existing behavior has change. Why should we use Regression Testing?There are many kinds...

Sunday, December 4, 2011

Test-Driven Development (TDD) in Agile

Test-Driven Development (TDD) in AgileTest-Driven Development (TDD) is a developer's process that focus on "Build the test first". First the developer creates the automated unit tests that defines a desired expectation of new function then produces code to pass that test. After that, developers refactor to optimize the code and then, retest it. Passing the tests confirms correct expected behavior as developers build and refactor the code. Test-Driven Development (TDD) process will help developers save their manpower for unit testing if they have...

Saturday, December 3, 2011

Pair Testing in Agile

Pair Testing in AgilePair testing is a practice which two team members are sitting together to test the software application on the same machine. The two team members can be between one tester and developer/business analyst/another tester. My team has applied this practice and these are benefits that I have found from Pair Testing. 1. Developers will know how testers do software testing. So, developers can apply test strategy for their own testing during coding. 2. Testers will have more idea about...

Friday, December 2, 2011

Software Testing in Agile

Software Testing in AgileSoftware Testing in Agile is a software testing practice which follows the rules of the Agile Manifesto. This agile testing practice involves testing from the customer perspective as early as possible, testing early and often because software will be released very often. To optimize the regression test effort and reduce the number of escaped bugs because of incremental development in agile testing, the automated testing should be used. Automated Testing...

Thursday, December 1, 2011

Development Model : Agile Software Development

Development Model : Agile Software DevelopmentWhat is Agile Software Development?Agile software development is a methodology based on incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. Agile ManifestoThe Agile Manifesto emphasizes that: 1) Individuals and interactions over processes and tools. 2) Working software over comprehensive documentation. 3) Customer collaboration over contract negotiation. 4) Responding to change over following a plan. That means we value...

Page 1 of 912345Next

Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More