Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.
Sign up to join this community
We have Several projects are lined up along with the product testing. Due to time urgency and time constraints the test cases are not writing up for some functions and UI and doing the testing without test cases. In this situation I felt and observed some bugs are raising in the client SIT environment testing. I know it is kind of bad approach in the testing.
Can anyone suggest me your feedback and ideas and this to avoid the leakage in the client environment.
Most Agile approaches suggest Test-Driven-Development, but at least you should practice some form of technical excellence to satisfy the following Agile principles:
Continuous attention to technical excellence and good design enhances agility.
Personally, I like the LeSS approach to technical excellence. A broad combination of quality practices.
Now in Agile teams, the question is not do we write tests or not, but who writes the test-cases. Developer should write test-cases, but testers could, product people could, anyone on the team could. Preferably the teams automate them aswell.
If your team does not have a nice balance of tests (unit, integration, and or end-2-end tests) then they are taking serious shortcuts and are cowboy coding in my book. With a high risk of very slow development in the long run, as:
Organizational Agility is constrained by Technical Agility
All Agile leaders suggest forms of testing in their writings, but I like those of Robert C. Martin the most. Be sure to read his Clean Code series starting with Clean Code: A Handbook of Agile Software Craftsmanship. Clean coders make tests period.
You are not Agile with just the process alone, I think we should talk more about the technical practices. An adaptable process is worthless if your product is not adaptable. Agile coding is all about refactoring and having a soft product that does not resist change. Testing is a strong part of this.
You should consider time-boxed exploratory testing and risk-based testing - both approaches have their benefits and compliment each other if you're able to execute them both.
Exploratory testing is an approach to software testing that is concisely described as simultaneous learning, test design and test execution.
Risk-based testing functions as an organisational principle used to prioritise the tests of features and functions in software, based on the risk of failure, the function of their importance and likelihood or impact of failure.
The latter is especially useful when pushed for time, as you're able to test the highest risk areas and have confidence that no high priority / severity defects exist in the product before handing over to the client.
