We at IT Engg Portal, provide all the Computer and IT Engineering students of Pune University with well compiled, easy to learn notes and other E-resources based on the curriculum
We provide the most recommended power point presentations and Video Lectures from the most prominent Universities for most of the difficult subjects to ease your learning process
Our Team has worked hard to compile this E-Book for all students heading for Campus Placements. The book is a complete solution for Technical Preparation for Campus Placements.
With more than 4,00,0000 pageviews from 114 countries over the globe, we are now the most viewed website for Ebooks and other E- Resources in Computer and IT Engineering
We use WinRunner as a load testing tool operating at the GUI layer as it allows
us to record and playback user actions from a vast variety of user applications
as if a real user had manually executed those actions. We use WinRunner in
addition to LoadRunner when we want to record user experience
response time. Visit
mercuryinteractive.com/products/WinRunner/for detailed information on WinRunner.
The following diagram shows how a GUI layer testing tool, such as WinRunner, operates.
The WinRunner screen print shown below simulates a user starting up an
Internet Explorer session and connecting to
www.google.com.au before performing a
Google search on the text: "Mercury Interactive".
As can be seen, WinRunner records each
of the actions that the user performed on the desktop to get to and search the
Google web site.
This is in contrast to the way that VUGen
records the protocol that the client application generates. However, both tools
have their part to play in a load
test.
The screen image below is a script example of how WinRunner recorded the events on the windows
desktop to "Press Start" and then Invoke Internet Explorer by selecting the
option marked "Internet". The text "google.com" was recorded as
being entered as a URL and the "return" key (<kReturn>) was then recorded so the
IE loaded the Google site into the browser window. The characters "Mercury
Interactive" were then recorded as they were typed into the Google search field,
followed by another <kReturn> to initiate the search.
As can be seen from this script example, WinRunner does nothing at the protocol layer (like VUGen would) but records and plays back user
events, so that the underlying application operates as if a person was sitting
at the desktop.
For WinRunner to operate, it needs to be in control of the PC, so that it can
execute the user actions that had been previously recorded. This is why
one can not execute a load test
with WinRunner as the means of load generation. In order to simulate 100
users, one would need 100 PCs with WinRunner on each PC.
However, WinRunner is a valuable piece of load testing technology when used
properly in a load test as it is
the only means of determining the actual
user response time, taking into account
the processing that is executed on the clients hardware. (As
VUGen operates at a protocol level it is only able to
measure at a protocol level.)
Please visit performance
tests and network
sensitivity tests for other testing situations where it is very appropriate
to use WinRunner. By using WinRunner in these situations, WinRunner usage
will be extended beyond automated functional testing, increasing it's value to
your testing team and organization.
Software Testing & Quality Assurance is a very important subject introduced in the curriculum of Computer and IT Engineering. The subject has immense application in the industry and is a subject of huge importance to freshers and also to students from campus placement point of view. Freshers are normally asked to start their career in Software Testing in most of big Companies like Infosys, Accenture etc. Students who belong to branches other than Computer and IT are mostly given the profile of a Software Tester as a fresher (most of them).
Apart from curriculum, most of the companies do ask questions on Software Testing in the Technical Interview . The questions are mainly to analyze a students awareness about various software testing techniques. Companies like Cybage, Persistant, KPIT Cummins, Harbinger, Syntel and most other IT companies usually ask most of the questions on Software Testing in the Technical Interview.
Moving on to the syllabus, the subject is a bit vast and a bit confusing (since it covers huge amount of theory). The subject is scoring to certain extent, i mean scoring 65-70 is not a difficult task. The syllabus for Computer and IT Engineering is quite different and not the same.
# Note - Software Testing & Quality Assurance is a subject -
Compulsory for IT Engineering (PU) [SEM 7]
Elective for Computer Engineering (PU) [SEM 7]
Syllabus for IT Engg :
Unit I Testing Principles Need of testing, Basic concepts – errors, faults, defects, failures, test bed, unit testing, integration testing system, system testing, regression testing, alpha, beta and acceptance testing , functional testing, performance testing, recovery testing, white box testing, black box testing, verification and validation
Unit II Test Management Testing Life Cycle – Roles and activities, Test Planning – forming a test team, develop test plan review Test Cases design strategies black box approach: random testing, equivalence class partitioning and boundary value analysis. white box approach: test adequacy criteria, coverage and control flow graphs, paths, loop testing, mutation testing. Test execution: build test data, life cycle of defect, defect tracking, defect detection stages, defect detection stages, defect types, defect severity, defect analysis and prevention.
Unit III Software Metrics Scope of software metrics, Classifying software measures, Measurement basics – representational theory, scales, meaningfulness, What to measure – GOM technique, Control flow structure, product quality metrics – MTTF, defect density, customer problems, customer satisfaction, function point, Metrics for software maintenance, In-process quality metrics.
Unit V Quality Standards Basic concept of – ISO 9000 & 9001, CMM, six sigma.
Unit VI Development of CMM CMM – Following KPAs : requirements management (RM), software project tracking and oversight (SPTO), software configuration management (SCM), organization process definition (OPD), software product engineering (SPE), peer reviews (PR), quantitative process management (QPM), defect prevention (DP), process change management
Syllabus for Computer Engineering Unit 1
Introduction, Basics of Software Testing, Testing Principles, Goals, Testing Life Cycle, Phases of Testing, Defects, Defect Life Cycle, Defect Report, Test Plan(IEEE format), Importance of testing in software production cycle.
Unit II Introduction, Need of black box testing, Black box testing Concept, Requirement Analysis, Test case design criteria, Testing Methods, requirement based testing, Positive & negative testing, Boundary value analysis, Equivalence Partitioning class, state based or graph based, cause effect graph based, error guessing, documentation testing & domain testing, design of test cases. Case studies of Black-Box testing.
Unit III Introduction, Need of white box testing, Testing types, Test adequacy criteria, static testing by humans, Structure - logic coverage criteria, Basis path testing, Graph metrics, Loop Testing, Data flow testing, Mutation Testing, Design of test cases. Testing of Object oriented systems, Challenges in White box testing, Case-study of White-Box testing
Unit IV Test organization, Structure of testing, Measurement tools, Testing metrics: Type of metric – Project, Progress, Productivity, Metric plan, Goal Question metric model, Measurement in small & large system. Other Software Testing: GUI testing, Validation testing, Regression testing, Scenario testing, Specification based testing, Adhoc testing, Sanity testing, Smoke testing, Random Testing. Advances in Software Testing Methods
Unit V Software quality, Quality attribute, Quality Assurance, Quality control & assurance, Methods of quality management, Cost of quality, Quality management, Quality factor, Quality management & project management, Software quality metrics-TQM, Six Sigma, ISO, SQA Model.
Unit VI Manual testing, Automated Testing Tools & Case studies, Study of Testing tools (QTP, Rational Robot, Winrunner, Loadrunner), Case studies based on Web based, GUI testing, Manual testing Vs Automated testing, Automated Testing Tools Case studies
