What should be the critieria for the selection of new feature test cases to be moved into build acceptance test suite?

As the requirement is to move new feature test cases to build acceptance suite, I think it is important to note, what benefits the build acceptance tests provide usually:
·         Fast feedback to developers, if there are issues in the checked-in code. 
·         Tester gets a working build to start with their activities
·         Application should be usable every time

Now for feedback to be faster, following are few points that need to be considered before test cases being moved to build acceptance suite –
o    The test cases must be / can be automated 100%, so that later no manual intervention is required.
o    The test cases can be executed in less time (its relative term but then fast feedback is also the same)

For testers to get a working build:
o    The build should be install-able correctly, so installation related test cases
o    Basic functionality (e.g. login, export etc.) of new features should be working, so that testers can verify additional test cases (boundary / negative)

For application to be usable every time:
o    Test cases covering business critical scenarios should be part of the build acceptance suite.


So, as per the above analysis, I don't consider that negative test cases or even boundary test cases should be part of build acceptance tests. I would be eager to find more inputs on these lines though.

Comments

Post a Comment

Popular posts from this blog

Performance Test Run Report Template

You have gathered requirements from clients, identified key critical business scenarios, analyzed the workload distributions, found out performance goals and requirements, identified  tool for generating load, setup the test environment, designed the scripts, executed the performance run, collected the raw data, analyzed it, what next?  Send information to stakeholders? No!!  Wait!! It needs to formatted, customized for different stakeholder(s) and reported accordingly. This article suggests one of the ways to report performance run results to client especially if the performance testing activity has been outsourced to yours company.  It discusses the performance report template and importantly the reasons for including the items in the report. The performance report template contains information by data collected from client side only and doesn’t discuss / talk about data from server side like processor utilization etc. Broadly the performance report has been divided in three major
Read more

Understanding Blockchain

This notes will cover below questions... Introduction to Blockchain What is the difference between Blockchain and Bitcoin? What are some other uses of blockchain that go beyond bitcoin? History of blockchain Could you explain the blockchain process in laymen terms? If all data is available to the public. Can anyone know my bank balance (in Bitcoin)? Introduction to Blockchain The Blockchain is a decentralized and distributed public (digital) ledger where transactions are recorded and confirmed anonymously. It’s a record of events that is shared between many parties. More importantly, once information is entered, it cannot be altered without altering subsequent blocks. WTF is the blockchain? A guide for total beginners What is the difference between Blockchain and Bitcoin? The blockchain is a technology
Read more

Bugs Management in Agile Project

Agile has a refreshing approach to bugs, especially when contrasted with traditional waterfall practices. Historically, teams would postpone bugs to a stabilization phase. This stabilization phase was long and tedious, typically with high stress and long hours. Agile, on the other hand, promotes the following thought processes: Carrying bug debt is unhealthy and sometimes, even destructive. We should fix bugs, not track them. A feature isn't done until the bugs are fixed. Quality is part of the overall cost. Bugs are prioritized against new features. A bug needs to be more important than the next new feature. Notes All new features have a "bug tail." The bug tail is the diminishing number of open bugs on the new functionality. When a feature is added, bugs are introduced. Most are discovered and fixed immediately by the team as a part of feature development: some a few days later, others not until long after a story is considered &quo
Read more