Skip to main content

Static Testing Activities

Static Testing
The simple static test is essential to detect the possible defects or errors during design stage of software applications & to verify in a precise modus or the various tasks for synthesis of program modules & the test plans. Some of activities that relate to the static testing involve desk checks, code inspections, or walkthroughs. You should also note that’s the static testing is conducted without need to execute the program. The software developer just requires to analyzing the data & the codes that are within program. One of important tasks of conducting the static testing is to search for the possible bugs in program. You can find the various bugs in software’s applications.
The two main activities of static testing are that:
·         Reviews
·         Testing with use of tools.
Review:
The Review activities of static testing can be formal & in-formal. The in-formal activities are used more often that formal, & in both cases, re-viewed document can be checked more than once. Another classification of re-view activities divides into three different groups:
·         Software walk-through.
·         Technical re-view.
·         Software’s inspection.
A Software walkthroughs & inspections are generally composite into peer’s re-views.
A Static testing with use of automated testing tool’s is effected prior of code run or help’s to inspect the design, code or other testing activities. This type of static testing that aims to checks the code of software’s & uses by the following tools:
·         Metrics of code.
·         Structure of code.
·         Code conformity with modern standards.

Benefits of Reviews:

·         Development productivity can be increased & time reduced.
·         Testing costs & time can be reduced through removing the main delays in test execution.
·         Reduction in life-time costs can be achieved.
·         Improved the communication outcomes as authors & discuss with peers.



Different objectives of re-views:

·         Finding Bugs
·         Generating discussions.
·         Gaining understanding.
·         Decision making by consensus.
Activities of formal Review:
The Reviews at more formal end of spectrum, such as technical re-views & inspections, share the certain characteristics of that different them from the less formal re-views of which walkthrough are a typical example.
Stages of formal reviews:
·         Planning
·         Re-view entry criteria
·         Kick-off
·         Review Meeting
·         Individual Preparation
·         Examine
·         Fixing Defects
·         Follow-up
·         Checking Exit Criteria
General role & responsibilities of different members in re-view team:
·         Manager
·         Moderator
·         Author
·         Re-viewers
·         Scribe


Comments

Popular posts from this blog

Steps To Hunt the Bugs Successfully

The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...

Cross browser testing Tools

Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...

Mobile Application Testing: Strategy for Development

There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...