Exclusively for you!! Trial version of Google Apps, Apply Coupon-CNHPGX6T6QRWGV!!
Software Testing Life Cycle (STLC)
Jan20

Software Testing Life Cycle (STLC)

Welcome to CodeSpread! Software Testing Life Cycle (STLC) is a process which consists of a number of phases to improve the quality of the product. Each phase involves various testing activities like Requirement Analysis Test Planning Test Design Test Environment Setup Test Execution Test Reporting   Requirement Analysis: What are the types of tests to be performed? Identify Modules. Is there scope for automation testing? Prepare Requirement Traceability Matrix (RTM). Testing Scope. Test Environment Details. Test Planning: What needs to be tested? Identify Test tool. Effort estimation and resource allocation. Scope of testing. Risk Identification. Training Requirements.. Test Design: Create test cases & test scripts. Review test cases & test scripts. Identifying test data, If Test Environment is available. Test Environment Setup: Prepare hardware and software requirement list for the Test Environment Perform Smoke testing. Test Execution: Execute the test cases. Report and log bugs to developers. Track defects to closure. Prepare list of defect status. Test Reporting: Prepare Test closure report. Prepare Defect Metrics. Prepare KT documents. STLC phases depends on the organization and their needs but the basic understanding remains the same across. Please mail at admin@codespread.com for...

Read More
Few lines on Exploratory testing
Dec16

Few lines on Exploratory testing

What is Exploratory testing? Exploratory testing by far is an approach to run and learn where testers do not create test cases beforehand. They usually gets acquainted with the system first. It provides a learning opportunity to the testers where they need to think before they begin creating or applying any test case. This is more of an ad-hoc approach where testers get a free hand on the system. Plus, this learning helps to write the test cases on the run. Why Exploratory testing? What is the need? Need is the current trend which says to identify bugs before the actual testing. Current trend emphasizes on the learning than the actual implementation. It is more about the Improvement which can be brought into the system beforehand. Exploratory testing is run by the data in hand and not the scripts. This approach widens the scope of testing. It helps the testers to understand the system, explore the system and reach the unexplored territories. With Exploratory testing, less preparation is required, important bugs are found quickly, and provides space for run-time learning. How Exploratory testing is different from Scripted testing? Scripted testing has many advantages like re usability, compliance and result oriented but when we compare it with exploratory testing; we know that, with scripted testing, testers always have test cases ready with them before they begin the testing. This limits their scope and they just need to compare the actual results with expected results. There is no dynamic learning and always a chance of random and sudden tweaks/ improvement in the testing approach. Conclusion: Both the approaches have their own advantages and shortcomings and both approaches exhibits same efficiency and result fulfillment. But we know, in some way, exploratory testing empathize learning and...

Read More
Short Note on Performance Testing
Jun25

Short Note on Performance Testing

Wikipedia says “performance testing is in general testing performed to determine how a system performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.” The focus of performance testing is checking a software program’s Speed, Scalability and Stability. The objective is to identify performance bottlenecks before the software application goes live. Before going for performance testing, ask for NFR document. A NFR document is called non-functional requirement document which specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. Typical non-functional requirements are: Performance – Response Time, Throughput, Utilization, Static Volumetric Scalability Capacity Availability Reliability Recoverability Maintainability Serviceability Security Regulatory Manageability Environmental Data Integrity Usability Interoperability Types of performance test: Load testing: checks application’s ability to  perform under anticipated user loads. This user load can be the concurrent number of users performing some operations within the set duration. Stress testing: testing an application under extreme workloads to see how it handles high traffic or data processing. This is related to conditions like if the current load goes well above the expected maximum. Endurance testing: to ensure the software can handle the expected load over a long period of time. Here, the main focus is on performance degradation under extended, significant period of time. Scalability testing: checks application’s effectiveness in ‘scaling up’ to support an increase in user load. Spike testing: tests the software’s  reaction to sudden large spikes in the load generated by...

Read More