Code testing practice
So now I have come to the conclusion like many others that having some way of constantly testing your code is good practice since it enables fewer people to be involved (colleges and customers alike) by simply knowing what’s wrong before someone else finds out the hard way.
Severity and relation to occurence – priority?
I have been browsing through some webpages related to testing and found one dealing with the metrics of testing. It says:
What Does It Usually Mean for a Feature to be “Supported”?
I’m currently working some testing for a particular area of an application. I had to write some automated tests for a particular feature but due to the circumstances, this was not easy to do. When I asked one of the other testers about it, he mentioned that the same features exist in a sister application our company produces but isn’t documented anywhere (end-user documentation or otherwise). He also said that the feature doesn’t typically get tested at all in the sister application and isn’t usually tested in the application I work on. Apparently this feature isn’t heavily used but removing it would require a fair bit of work so the benefit-cost ratio doesn’t work out.
What Does It Usually Mean for a Feature to be “Supported”?
I’m currently working some testing for a particular area of an application. I had to write some automated tests for a particular feature but due to the circumstances, this was not easy to do. When I asked one of the other testers about it, he mentioned that the same features exist in a sister application our company produces but isn’t documented anywhere (end-user documentation or otherwise). He also said that the feature doesn’t typically get tested at all in the sister application and isn’t usually tested in the application I work on. Apparently this feature isn’t heavily used but removing it would require a fair bit of work so the benefit-cost ratio doesn’t work out.
Does software testing methodology rely on flawed data?
It’s a well-known fact in software engineering that the cost of fixing a bug increases exponentially the later in development that bug is discovered. This is supported by data published in Code Complete and adapted in numerous other publications.
Is deserializing complex objects instead of creating them a good idea, in test setup?
I’m writing tests for a component that takes very complex objects as input. These tests are mixes of tests against already existing components, and test-first tests for new features.
Introducing a (new) test method to a team [closed]
Closed 9 years ago.
Who are ‘users’ in testing?
Having e.g. a system for booking flights, during UAT it is not being tested by real users (customers who will buy tickets) rather than people from the client side who will just simulate this. Are there any more specific terms to distinquish between real users (like end user) and users doing the UAT?
How come verification does not include actual testing?
Having read a lot about this topic — such as on this Software Testing Fundamentals site on verification and validation and Software Testing and Quality Assurance: Theory and Practice by Naik and Tripathy — I still do not get it. Verification should prove that you are building the product right, while validation proves that you built the right product. But only static techniques (code reviews, requirements checks…) are mentioned as being verification methods. How can you say if its implemented correctly if you do not test it? It is said that verification ensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does.
How do I hire testers by giving them a buggy app for testing their efficiency?
My boss wants to recruit testers based on their testing efficiency (number of bugs identified). So, he’s shortlisted 5 people and I need to give them an app full of bugs and see how they fare in reporting obvious bugs, and hidden bugs. I know…. it kind of sounds weird. I guess, this is just like the coding world, where you hire a programmer by assessing his/her programming ability (which is a little easier). Once hired, these testers would be testing a java swing app, so their familiarity of testing frameworks/tools is not really required.