Skip to main content

Avoid 10 Worst Practices In Software Testing

Testing is performed to ensure the quality of the deliverables to the user. However, the most companies not treating testing as the part of their project. As a result, probably less effort into the software testing than other parts of the project. It is essential to aware that underestimating the testing may lead to face several consequences. Particularly, putting less effort on testing than one should do, will result in severe mistakes in the future. This blog walks through some worst practices in software testing that needs to be avoided.

Worst Practices In Software Testing:
  1. Not Having Professional/Experienced  Tester To Manage To Test:  Still, it is possible to come across the organization where business analysts or developers do testing. Allowing developers to handle testing might increase the chance of missing the semantic/syntactic bugs detections. Testing software in all possible views requires the professional perspective of testers. Developers sometimes rush this phase to meet the project deadlines, which would result in bad code.
  2. Insufficient Time For Testing:  In most organizations, the testing phase to rush to balance any delays from the upstream stages. The upstream phases like the design or implementation stages of the SDLC cause pressure, resulting in software with poor quality, to reach the “time-to-market” goal. They underestimate the consequence of compromising testing for a business reason.
  3. Not Determining The Root Cause:  Testers not analyzing the bugs or defects determined in the testing to find the root cause. RCA (Root Cause Analysis) supports to minimize the defects in succeeding releases. Determining defect’s root cause can enhance the competency to fix it that guarantees other related bugs don’t arise due to that certain root cause.
  4. Improper Mindset: Team mindset also influences to the certain extent in the performance of the testing. Software testing is the job that needs designated person to be very meticulous. If the organization fails to create a bug-conscious culture by offering the adequate resources, knowledge, and tools, it will affect the mindset of the testers resulting less concentration on their dedicated work. This scenario will lead more bugs that will slip via the cracks.
  5. Overlooking Unimportant Bugs: Just because a bug looks insignificant when it was discovered does not denote it must be dismissed quickly. It might potentially root to a larger problem, or may even be connected to another issue. Each and every bug found need further investigation regardless of big or small.
  6. Poor Bug Reporting: The job of testers involves more than testing functions. In addition to finding bugs as well as designing flaws, reporting those finds is an important work for the testers. Most of the bug reports are poor in quality. The bug reports are not supporting the developers and lacking essential information like a description of the priority of the bug, what went wrong and more.
    At least a bug report should include the following details: Who did the test
    Date of tests
    Test Result
    Main data points applied in the testing
  7. Failure To Find High-Risk Areas: Undoubtedly, there will be areas that are riskier than other areas of the software. Those parts will need extra attention. Failing to determine high-risk areas will route to a myriad of wasted testing time. This will result in efforts misplaced and applied in areas, which don’t demand such scrutiny.
  8. Following A Blindfolded Approach: Some testers don’t do any planning and begin testing blindly. They are not understanding and even knowing what other testers are doing and what they are focusing on. These results lack awareness on the scenarios as well as the features they were missed out.
  9. Not Prepared With Required Tools Before Testing: Before beginning testing, testers do not check for the appropriate technologies and tools to mitigate bugs clearer and quicker. They are not checking the tools for taking screenshots, getting the logs, recording your screen, and add-ons for recording additional details to insert to the bug reports. This will increase the likelihoods of the bugs remains undetected.
  10. Not Examining The Requirements Thoroughly: The most costly and biggest mistake that testers do is not reading or analyzing the requirements. Failed to spend at least 5 minutes to read and understand the information and client requirements that would be helpful for testing, makes them spend more time on categorizing or prioritizing the threats. For example, after spending 30 to 60 minutes in the testing as well as logging bugs, they would mark certain bugs as out of scope or invalid. This is because they didn’t examine the requirements clearly or didn’t understand the exact requirement clearly.
Thorough testing is important for software quality assurance. Avoiding the worst practices in the software testing can produce high-end software

Comments

Post a Comment

Popular posts from this blog

Mobile Application Testing Checklist

1. DEVICE SPECIFIC CHECKS 1.1  Can the app be installed on the device? 1.2 Does the app behave as designed/desired if there is an incoming call? 1.3 Does the app behave as designed/desired if there is an incoming SMS? 1.4 Does the app behave as designed/desired if the charger is connected? 1.5 Does the app behave as designed/desired if the charger is disconnected? 1.6 Does the app behave as designed/desired if the device goes to sleeping mode 1.7 Does the app behave as designed/desired if the device resumes from sleeping mode 1.8  Does the app behave as designed/desired if the device resumes from lock screen? 1.9    Does the app behave as designed/desired if the device is tilted? 1.10  Does the app behave as designed/desired if the device is shaken? 1.11 Does the app behave as designed/desired if a local message is coming from another app (think   of: calendar reminders, to-do task etc.). 1.12 Does the app behave as designed/desired if a push message i...
Post a Comment
Read more

Test Scenarios for Excel Export Functionality

1. The file should get exported in the proper file extension. 2. The file name for the exported Excel file should be as per the standards e.g. if the file name is using the timestamp, it should get replaced properly with an actual timestamp at the time of exporting the file. 3. Check for date format if exported Excel file contains the date columns. 4. Check number formatting for numeric or currency values. Formatting should be the same as shown on the page. 5. The exported file should have columns with proper column names. 6. Default page sorting should be carried in the exported file as well. 7. Excel file data should be formatted properly with header and footer text, date, page numbers etc. values for all pages. 8. Check if the data displayed on a page and exported Excel file is the same. 9. Check export functionality when pagination is enabled. 10. Check if export button is showing proper icon according to the exported file type E.g . Excel file icon for xls files 11. ...
Post a Comment
Read more

Software Testing Tips

Here are some of the Best Testing Practices which I learned by Experience:  1) Learn to analyze your test results thoroughly. Do not ignore any test result. The final test result may be ‘pass’ or ‘fail’, but troubleshooting the root cause of ‘fail’ will give you the solution of the problem. Testers will be respected if they not only log the bugs but also provide solutions. 2) Learn to maximize the test coverage each time you test any application. 100% test coverage might not be possible but still, you can always try to reach near it. 3) In order to ensure maximum test coverage, break your application under test (AUT), into smaller functional modules. Write test cases on such individual unit modules. Also if possible break these modules into smaller parts. E.g : Lets assume that you have divided your website application in modules and ‘accepting user information’ is one of the modules. You can break this ‘User information’ screen into smaller parts for writing ...
Post a Comment
Read more