Test Responsibility Matrix (TRM) / Test Matrix (TM) Test deliverables. Manual Testing Concepts . Ex: Life Cycle Testing. The validation of final product before releasing to the customer is called as SQC. In the above Software Development process, testing is been conducted as a single stage by the development team. To improve quality in software development process, project management should concentrate on multiple stages of development with multiple stages of testing. Fish model software development: Upper angle is life cycle development and lower angle is life cycle testing. Information gathering defines what and Analysis defines how. BRS: Business requirement specification defines the requirement the customer to be developed as software. This document is also known as Customer Requirement Specification (CRS) or User Requirement Specification (URS). SRS: Software requirement specification defines functional requirements to be developed and system requirement to be used (Hardware and Software). Example: BRS defines addition (Customer requirement). SRS defines how to solve customer requirement. Review: It is a static testing technique. In this review responsible people will estimate completeness and correctness of corresponding documents. HLD: High Level Design document defines the overall architecture of the system from root functionalities to leaf functionalities. This HLD is also known as Architectural Design or External Design. LLD: Low Level Design document defines the internal logic of corresponding module (or) functionality. The LLD is also known as Internal Logic Design document. On request from may readers I am updating sample bug report on separate page. Here are couple of sample bug reports and treat them as samples only. This is the guest post from Vijay D (Coincidence with my name). Below sample bug/defect report will give you exact idea of how to report a bug in bug tracking tool. 4+ Years Experienced Manual Tester Resume K Vijay Rao +91-***** vijay Bug triage Meeting Process step by step - A bug triage meeting should be held regularly during the construction phase (or testing cycle) of a project. Manual Testing Interview Questions - 1 Manual Testing Interview Questions - 2 Manual Testing Interview Questions - 3 Manual Testing Interview Questions - 4. Discussion; RE: CV for Software Testing - sample CV -Bhardwaj Rahul (09/07/12) Telecom testing profile - CV sample and formats Manoj KUMAR, Phone: +9191. Test Status Report Test Status Reporting is a formalized reporting on the status of the project from a testing point of view. This is part of the project. Prototype: A sample model of an application without functionality is called prototype. Program: A set of execute statements is called a Program. Module: A set of programs is called as a Module or Unit. Build: The set of modules is called as Software Build or Product. White Box Testing: It is a coding level testing technique to verify the completeness and correctness of program structure. Programmers will follow this technique. It is also known as Glass Box Testing (or) Clear Box Testing (or) Open Box Testing. Black Box Testing: It is a build level testing technique. In this testing test engineers will validate every feature depending on external interface. Software Testing: The Verification and Validation of a software application is called software testing. Verification: Are we building the product right? Validation: Are we building the right product? V stands for Verification and Validation. This model defines mapping between development process and testing process. The real V- model is expensive to follow for small and medium scale organizations. Due to this reason, small and medium scale organizations maintains separate testing team for System Testing phase. In general the software development process starts with requirements gathering and analysis. In this phase business analyst category people will develop BRS and SRS. After development of the documents the same business analyst category people will conduct review meetings to estimate completeness and correctness of the documents. In this review meeting, the same business analyst category people will concentrate on below checklist. The same design category people will conduct review meetings to estimate completeness and correctness of the design documents. In the review the same design category people will concentrate on below checklist HLD ? Do they handle errors? After completion of design and their reviews, programmers will concentrate on coding to construct software physically. In this phase programmers will test every program through a set of white box testing techniques w. LLD. 1. Basis paths testing. Control structure testing. Program technique testing (Time). Mutation Testing. In this coverage programmers will verify the execution of program without any syntax and run time errors. In this coverage programmers will execute a program more than one time to cover all areas of that program coding while running. In this coverage programmers will concentrate on correctness of the program functionality. In this coverage programmers will check statements in the program including variables declaration, IF conditions, Loops, etc. If the execution time is not reasonable then the programmers will change the structure of the program without disturbing functionality. After completion of a program testing, the corresponding programs will review the completeness and correctness of the program testing. Mutation means that a change in coding of the program, in this Mutation testing programmers will perform changes in various areas in the program and repeat previously completed tests. If all the tests are passed on the changed program, then the program will continue testing on some program. If any one of the tests is failed on the change in program, then the program will concentrate on further coding. Note: in white box Testing techniques, the first 3 techniques will test program code and the mutation testing will estimate the completeness and correctness of the test on the program. After completion of dependent programs development and unit testing, programmers will inter connect the programs to construct a complete software build. In this stage programmers will verify integration of programs in four types of approaches. Top Down Approach. Bottom Up Approach. Hybrid Approach. d. System Approach. In this approach the programmers will inter connect main models to some of the modules in the place of remaining sub modules programmers will use temporary programs called Stubs. In this approach the programmers will inter connect sub modules without connection to the main module. Programmers will use a temporary program instead of main module called Driver. It is a combined approach of Top Down and Bottom Up approaches. This approach is also known as Sandwich approach. It is also known as Final Integration (or) Big Bang Approach. In this integration programmers will inter connect programs after completion of total development. Note: In general the programmers will inter connect programs through any one of the above methods depending on circumstances. After completion of Integration Testing, and receiving the build from development team, the testing team will concentrate on system testing to conduct using Black Box Testing techniques. System Testing is divided into 3 sub stages. Usability Testing. Functional Testing. Non- Functional Testing. After receiving software build from development team, the testing team will conduct usability testing. In this test the testing team will estimate “User Friendly ness” of all screens in the software build. There are two sub tests. User Interface Testing or UI Testing. In this test, the testing team will apply below 3 factors on every screen of the software build. These help documents are also known as User Manuals. Case Study: It is a mandatory testing level in testing team responsibilities. During this test, testing team will concentrate on “Meet customer Requirements” through below sub tests. Requirement Testing. Sanitation Testing. Requirements Testing. It is also known as Functionality Testing. During this test the responsible testing team will apply different coverage techniques as discussed below on the functionalities of software build. This testing is also known as garbage testing. After completion of user interface and functional testing, the testing team will concentrate on Non- Functional Testing to validate quality characteristics of software build Like Security and Performance. Recovery Testing. This testing is also known as Reliability Testing. During this test, the testing team will validate that whether the software build is changing from abnormal state to normal state. Compatibility Testing. It is also known as Portability Testing. During this test, the testing team will validate that whether the software build is running on the customer expected platforms or not? Configuration Testing. It is also known as hardware compatibility testing. During this test the testing team will validate that whether the software build is supporting different technology hardware devices or not? Example: Different technology printers. Different topology networks, etc. During this test the testing team will validate that whether the software build co- exists with other software applications to share common resources. Example: Sharing data, sharing hardware devices, printers, speakers, sharing memory, etc. The testing team is practice installation of software build in to that environment. Load Testing. The execution of the software build under customer expected configuration and customer expected load to estimate speed of processing is called as load testing. Here, load means that the no of concurrent users working on the software. This is also known as scalability testing. Stress Testing. The execution of the software build under customer expected configuration and various load levels from low to peak is called stress testing. In this testing, testing team will concentrate on load handling by the software build. Storage Testing. Testing whether the system meets its specified storage objectives. Testing the data of different formats and in different devices. Verifying the efficiency of data storage in devices and proper retrieval of the data. Data Volume Testing. Volume testing refers to testing a software application with a certain amount of data. This amount can, in generic terms, be the database size or it could also be the size of an interface file that is the subject of volume testing. For example, if you want to volume test your application with a specific database size, you will expand your database to that size and then test the application’s performance on it. Example: MS Access technology support 2. GB of database as maximum. Parallel Testing. It is also known as Comparative Testing. During this test, the testing team will compare the software build with other competitive software in market or with old version of same software build to estimate completeness. This is applicable only for software product but not on software applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |