software testing notes for 6th sem ise vtu notes
#1
Sad 

 i would like to get details on software testing notes for 6th sem ise vtu notes ..My friend Justin said software testing notes for 6th sem ise vtu notes 
Reply
#2
Ghfhjzfxhkbj gzuvkjcgzhcivk lzkgzifzyofupclhzfzgkxuvicudugovkvjciv
Reply
#3

Manual Testing Guide
Software Testing: Testing is a process of executing a program with the intent of finding error.

Software Testing are contains two types:

1) Manual Testing and,
2) Automation Testing

Manual Testing:
Manual testing is the process of manually testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases

Software Testing Definition: Testing is the process of executing a program with the intention of finding errors.

Drawbacks of Manual Testing

(i)Time consuming.
(ii) More resources required.
(iii)Human Errors
(iv)Repetition of the Task
(v)Tiredness
(vi)Simultaneous auctions are not possible (Parallel)


Software Engineering: Software Engineering is the establishment and use of sound engineering principles in order to obtain economically software that is more reliable and works efficiently on real machines.

Software engineering is based on Computer Science, Management Science, Economics, Communication Skills and Engineering approach.

What should be done during testing?
Confirming product as
Product that has been developed according to specifications
Working perfectly
Satisfying customer requirements
Why should we do testing?
Error free superior product
Quality Assurance to the client
Competitive advantage
Cut down costs
How to test?
Testing can be done in the following ways:
Manually
Automation (By using tools like WinRunner, LoadRunner, QTP …)
Combination of Manual and Automation.
Software Project: An individual or collaborative enterprise planned and designed to achieve an aim.

Information Gathering – Requirements Analysis – Design – Coding – Testing – Maintenance: Are called as Project

Software Development Phases:
Information Gathering: It encompasses requirements gathering at the strategic business level.

Planning: To provide a framework that enables the management to make reasonable estimates of
Resources
Cost
Schedules
Size
Requirements Analysis: Data, Functional and Behavioral requirements are identified.

Data Modeling: Defines data objects, attributes, and relationships.
Functional Modeling: Indicates how data are transformed in the system.
Behavioral Modeling: Depicts the impact of events.
Design: Design is the engineering representation of product that is to be built.

Data Design: Transforms the information domain model into the data structures that will be required to implement the software.
Architectural design: Relationship between major structural elements of the software. Represents the structure of data and program components that are required to build a computer based system.
Interface design: Creates an effective communication medium between a human and a computer.
Component level Design: Transforms structural elements of the software architecture into a procedural description of software components.
Coding: Translation into source code (Machine readable form)
Testing: Testing is a process of executing a program with the intent of finding error
Unit Testing: It concentrates on each unit (Module, Component…) of the software as implemented in source code.
Integration Testing: Putting the modules together and construction of software architecture.
System and Functional Testing: Product is validated with other system elements are tested as a whole
User Acceptance Testing: Testing by the user to collect feed back.
Maintenance: Change associated with error correction, adaptation and enhancements.
Correction: Changes software to correct defects.
Adaptation: Modification to the software to accommodate changes to its external environment.
Enhancement: Extends the software beyond its original functional requirements.
Prevention: Changes software so that they can be more easily corrected, adapted and enhanced.
Business Requirements Specification (BRS): Consists of definitions of customer requirements. Also called as CRS/URS (Customer Requirements Specification / User Requirements Specification)

Software Requirements Specification (S/wRS): Consists of functional requirements to develop and system requirements(s/w & H/w) to use.

Review: A verification method to estimate completeness and correctness of documents.

High Level Design Document (HLDD): Consists of the overall hierarchy of the system in terms of modules.

Low Level Design Document (LLDD): Consists of every sub module in terms of Structural logic (ERD) and Backend Logic(DFD)

Prototype: A sample model of an application without functionality is called as prototype(Screens)

White Box Testing: A coding level testing technique to verify completeness and correctness of the programs with respect to design. Also called as Glass BT or Clear BT

Black Box Testing: It is a .exe level of testing technique to validate functionality of an application with respect to customer requirements. During this test engineer validate internal processing depends on external interface.

Grey Box Testing: Combination of white box and black box testing.

Build: A .Exe form of integrated module set is called build.

Verification: whether system is right or wrong?

Validation: whether system is right system or not?

Software Quality Assurance(SQA): SQA concepts are monitoring and measuring the strength of development process.
Ex: LCT (Life Cycle Testing)

Quality:
Meet customer requirements
Meet customer expectations (cost to use, speed in process or performance, security)
Possible cost
Time to market
For developing the quality software we need LCD and LCT

LCD: A multiple stages of development stages and the every stage is verified for completeness.

V model:

Build: When coding level testing over. it is a completely integration tested modules. Then it is called a build. Build is developed after integration testing. (.exe)

Test Management: Testers maintain some documents related to every project. They will refer these documents for future modifications.
Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page
Popular Searches: elearning notes for 6th sem ec vtu, sjbit software testing notes for 6th sem, software project management notes from notesengine, vtu 6th sem ise software testing notes, st notes vtu pdf, vtu filestructure notes, information systems notes of 7 sem ise vtu,

[-]
Quick Reply
Message
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  7th sem cse sunstar download 1 1,226 03-02-2021, 02:09 PM
Last Post: achar3729
  Request for 8th sem sunstar exam scanner 2020. 0 3,525 11-07-2020, 09:56 AM
Last Post:
  Beautician course notes in hindi 0 5,804 24-02-2020, 04:31 AM
Last Post:
  free download ksc m3 textbook vtu 1 2,985 11-12-2018, 10:50 PM
Last Post:
  mom 3rd sem be book by jbk das download 0 6,371 02-11-2018, 01:58 AM
Last Post: Guest
  software testing lab viva questions and answers vtu 0 5,287 30-10-2018, 02:09 AM
Last Post: Guest
  maruti suzuki dms software download 0 2,524 22-10-2018, 09:46 PM
Last Post: Guest
  vtu be me 5th sem dom j b k das test book download free 0 3,869 07-10-2018, 08:26 PM
Last Post: Guest
  computer graphics notes hindi pdf free download 1 1,366 21-08-2018, 05:07 PM
Last Post: Dharmesh Sankhla
  relay performance testing with high technology pdf 0 2,074 20-08-2018, 10:35 PM
Last Post: Guest

Forum Jump: