Dear Blog Readers,
Categories: Software Testing
Categories: Code Based Testing, Code Metrics, Java, Lessons Learned, Software Development, Software Metrics, Software Testing, Static Analysis, Technology, Test Management, Test Methodologies, Thoughts, Tools, Unit Testing, Whitebox Testing
Most of the Static Analysis tools over the application code helps us to identify the cyclomatic complexity (nonlinear paths) at a method level. These might be helpful to validate those methods and to achieve good code coverage over the same.
But the Code coverage at a Unit Level may not be a big help since most of the end user scenarios won’t run after unit level paths. These paths is an integration of the above unit level paths.
Since the Testers focus on simulating the end user scenarios, it will be good to identify all the possible nonlinear paths around the application code base and capture the code coverage based on these paths.
You might want to go through some discussion around this on Linkedin Answers
In case you have similar experiences over white box testing drop me a mail at email@example.com
Powered by ScribeFire.
Categories: Articles, Project Management, Software Development, Software Testing, Technology, Thoughts
Software Testing is considered as a Cost for some Stakeholders & an Investment for others in their context of operation. It’s good to know the status in your context. I had this query in LinkedIn Answers & thought of sharing the good discussion to my blog readers.
Categories: Articles, Bug Tracking, Code Metrics, Lessons Learned, Metrics, Project Management, Software Metrics, Software Testing, Technology, Test Metrics, Thoughts, Tools
Bug Database for the products might have thousands of issues over a period of time against various builds and releases. Though these issues fixed over a period of time, it might be hard to derive meaningful metrics over the release.
We need to support these releases over the production systems & it might be helpful to capture the hotspots / risk elements with the release. Most of the issues here to deal with the respective features, compatibility with other features / technologies & performance related issues.
The usual metrics of number of issues against a module and their severity levels may not be of help always.
How easy is it to derive the following from the Bug Database for a given release
- Identify the issues have originated from Requirements, Design & Implementation
- Identify the issues over their category (Functional, Performance, Security, Compatibility, Usability etc)
- Identify the issues along with their origin & category over the features rather than the modules / components
Powered by ScribeFire.
Categories: Articles, Bug Tracking, Lessons Learned, Software Testing, Technology, Test Documentation, Test Management, Test Methodologies, Testing Tools, Thinking like a Tester
In this post, i will explore different stages of the Bug from it’s inception to closer. The Bug has been found and logged into the Bug Tracking System. It’s my fourth post in the Bug Life Cycle series.
- The Bug has been found and logged into the Bug Tracking System. It will be treated as New Bug in the System.
- The Bug will be assigned to the concerned Developer for a Resolution.
- The developer looks in to the possibilities of the resoultion & takes a call on Resolution by fixing it or differing over the information provided.
- Tester validates the resolved issue in the build & checks for the regression scenarios over the fix.
- If the issue found fixed, then he choose to Close the issue else he / she will Re-open the same.
- The Cycle follows again for the re-opened issue till it get’s closed.
It worth doing the following activities
- Capturing the required and re-usable info to the Bug Report at it’s each stage.
- Check for all the closed bugs of Severity 1 & 2 against final build for the release.
In the next post, I will share my thoughts on the useful metrics over the Bug Tracking Repository.
Categories: Code Based Testing, Lessons Learned, Software Testing, Test Strategy, Whitebox Testing
The popular myths around Blackbox & Whitebox Testing are by it’s name. It’s black since we can’t see it (don’t have access to the code) & it’s white since you have access to all the code. But then, With in the code there are many black boxes inside and it’s tough to have access to that code base.
- We don’t have access to code of a language API. Most of the applications have been built on top of a API & assume that the API works fine
- Most of the application do integrate some third party tools over it’s API. We don’t have access to that code base.
- We don’t have access to the code of Compiler
- We don’t have access to code of rum time engine that executes our application code
- We don’t have access to the code of Operating System Services on top of which the application runs
The list goes on and there are many black boxes in side our code too. We are just testing the code written for the application and it’s better to call it as Code Based Testing rather than Whitebox Testing
– Happy Testing..
Categories: Bug Tracking, Lessons Learned, Software Development, Software Testing, Technology, Test Documentation, Thinking like a Tester, Thoughts
Today, i have come across an interesting issue with BSNL Portal. I have been using this site for online billing and payments for about an year.
Followed the usual steps and my objective is too see the bill and pay it online. To my surprise, the system says
This error message ” Invalid object name ‘RECEIPT_MASTER’ “ is strange and there is no information for me on how do i proceed further. The application might be unable to get the specified object from the Database.
In case if this happens on the last day of the payment, on line users are liable for late payment charges due to this issue.
Users are familiar with the messages like, Unable to process the information as of now & please check back after some time.
The error messages must be meaningful to the business users and we need to make sure that the technology related terms / phrases are not part of the same.
Powered by ScribeFire.