Interview Questions, Answers and Tutorials

Blog

Types of Software Testing

Software testing is the process of executing software in a controlled manner. When the end product is given to the client, it should work correctly according to the specifications and requirements stated by the client. A defect in software is the variance between the actual and expected results. There are different types of testing procedures, which when conducted, help to eliminate the defects from the program. Testing is a process of gathering information by making observations and comparing them to expectations. – Dale EmeryIn our day-to-day life, when we go out, shopping for any product such as vegetables, clothes, pens,…

Integration Testing Vs. System Testing

In software testing, there is often integration testing is pitched against system testing, due to the fact that integration and system testing are often interchanged with each other or considered to be synonyms for the same type of testing. However, at the very outset, I would like to clear that they are not synonyms and are indeed different types of testing… Software testing is a process that consists of dynamic and static activities, which concerns itself with the evaluation of software products to determine that the software indeed does meet the requirements of the end-user, and also to demonstrate that…

Testing Metrics

Testing Metrics METRIC is a measure to quantify software, software development resources, and/or the software development process. Metrics enable estimation of future work.A Metric can quantify any of the following factors:– Schedule,– Work Effort,– Product Size,– Project Status, and– Quality Performance   Project Management MetricsSchedule Variance (SV)This metric gives the variation of actual schedule vs. planned schedule. This metric is represented as a percentage.SV = [(Actual number of days – Planned number of days) / Planned number of days] * 100 Effort Variance (EV)This metric gives the variation of actual effort vs. estimated effort. This metric is represented as a…

Difference between QA and QC

Software testing is a process of verifying and validating that a software application or program meets the business and technical requirements that guided its design and development, and works as expected. Software testing also identifies important defects, flaws, or errors in the application code that must be fixed. Quality means the conformance to the specified design requirement. Being correct, the minimum requirement of quality means performing as required under specified circumstances. Debugging, a narrow view of software testing is performed heavily to find out design defects by the programmer. Quality Assurance (QA) is the process that focuses upon each and…

Performance testing with pyUnitPerf

Summary: If you are familiar with Mike Clark‘s JUnitPerf framework, then you may be interested in knowing that I have just released a Python port: pyUnitPerf. You can browse the source code here and you can get a gzipped tarball from here.Details pyUnitPerf tests are meant to transparently add performance testing capabilities to existing pyUnit test suites. The pyUnitPerf framework introduces 2 new types of tests: TimedTest: runs an existing pyUnit test case by imposing a limit to the time it takes to run the test LoadTest: runs an existing pyUnit test case by simulating concurrent users and iterations Let’s…

V Model to W Model | W Model in SDLC Simplified

We already discuss that V-model is the basis of structured testing. However, there are a few problems with V Model. V Model Represents one-to-one relationship between the documents on the left-hand side and the test activities on the right. This is not always correct. System testing not only depends on Function requirements but also depends on technical design, architecture also. A couple of testing activities are not explained in the V model. This is a major exception and the V-Model does not support the broader view of testing as a continuously major activity throughout the Software development lifecycle.   Paul…

V-model is the basis of structured testing

You will find out this is a great model! V-model is the basis of structured testing The left side shows the classic software life cycle & the Right side shows the verification and validation for Each Phase Analyze User requirements End users express their wish for a solution for one or more problems they have. In testing, you have to start preparing for your user tests at this moment! You should do test preparation sessions with your acceptance testers. Ask them what causes they want to test. It might help you to find good test cases if you interview end-users…

Art of Test case writing

Objective and Importance of a Test Case – The basic objective of writing test cases is to ensure complete test coverage of the application.  The most extensive effort in preparing to test software is writing test cases. Gives better reliability in estimating the test effort Improves productivity during test execution by reducing the “understanding” time during execution Writing effective test cases is a skill and that can be achieved by experience and in-depth study of the application on which test cases are being written. Documenting the test cases prior to test execution ensures that the tester does the ‘homework’ and…

Testing Stop-Process

This can be difficult to determine. Many modern software applications are so complex and run in such as interdependent environment, that complete testing can never be done. “When to stop testing” is one of the most difficult questions to a test engineer. Common factors in deciding when to stop are:   Deadlines ( release deadlines, testing deadlines.) Test cases completed with certain percentages passed Test budget depleted Coverage of code/functionality/requirements reaches a specified point The rate at which Bugs can be found is too small Beta or Alpha Testing period ends The risk in the project is under an acceptable…

Testing Start Process

Testing is sometimes incorrectly thought of as an after-the-fact activity; performed after programming is done for a product. Instead, testing should be performed at every development stage of the product. Test data sets must be derived and their correctness and consistency should be monitored throughout the development process. If we divide the lifecycle of software development into “Requirements Analysis”, “Design”, “Programming/Construction” and “Operation and Maintenance”, then testing should accompany each of the above phases. If testing is isolated as a single-phase late in the cycle, errors in the problem statement or design may incur exorbitant costs. Not only must the…