TEST PLANNING

week 2:

Assignment 1:

1. Who prepares test plan document ?

test lead or manager.

2. process to create test plan document ?

1. Write the introduction. …
2. Define your objectives. …
3. Write a section on required resources. …
4. Write a section on risks and dependencies. …
5. Write a section on what you are going to test. …
6. Write a section on what you will not be testing. …
7. List your strategy. …
8. Develop pass/fail criteria.

3. difference between test plan and test strategy ?

Test strategy is a high level document which defines the approach for software testing. It is basically derived from the Business Requirement document. Test strategy is developed by project manager or business analyst.

Test plan is derived from SRS (Software Requirement Specification) which is prepared by test lead or manager. The main goal of test plan is to include all the details related to testing such as what to test, when to test, how to test and who will be the tester.

4. Defect rejection and leakage ratio ?

Defect rejection ratio is the ratio of total rejection to total production and defect leakage is the ratio of total possibility of rejection occurrence to the total production.

5. Entry, exit and suspension criteria ?

Entry and exit criteria are the conditions which when satisfies; the test team starts (enters) the testing process and stops (exits) it. Suspension criteria is a condition in which the testing team temporarily suspends the testing process.

6. When do you start and stop testing ?

You start testing once you are clear with the requirements and the documents are ready.

you stop testing when there is Reduce in defects, Increase in Testing cost, Delivery dates.

7. Purpose of having a test plan document ?

We create a test plan because we want a document that describes the objectives, scope, approach and focus of the software testing effort.

8. how do you perform test estimation ?

It depends on how big the software is and based on resource, time, human skill and cost.

9. difference between beta and pilot testing ?

Pilot testing involves having a group of end users try the system prior to its full deployment in order to give feedback on its performance. Beta testing is testing of the product in the user environment.

10. risks to be avoid in testing ?

• Tight timelines
• Undefined project scope
• Insufficient resources
• Continuously changing requirements
• Natural disasters

 

11. counter measure taken by managers to avoid risk ?

1. Identify the Risks
2. Analyze Impact of each Identified Risk
3. Take counter measures for the identified & Analyzed risk

 

 

METHODOLOGY & OVERVIEW

WEEK 1:

ASSIGNMENT 5:

1. How does testing happen in agile environment ?

The whole team is responsible for quality rather than just the testing team or a particular role. Organizations have realized that defects encountered downstream are expensive and building quality within the code is important. Hence, in an agile world, even before the code has been written, testing is introduced in the process. Techniques such as Test Driven Development (TDD) focus on developer writing a test case even before functional code has been written.

Testers in an agile world are more of jack-of-all-trades and master of a few. Secondly, automation plays a key role in agile testing as it helps teams get rapid feedback on quality in real-time. Testers therefore need to be more open to implementing automation frameworks.

2. why do organizations prefer agile methodology rather than water fall or any other ?

In waterfall model the software is delivered at the very end, so if any change in requirements from the customer side, it is difficult to implement them.

In agile model the customer can see the product before release through sprint and meetings, so if any new requirements are made, it can be implemented easily.

3. key benefits for the team that follows agile methodology ?

Agile methods can help teams manage work more efficiently and do the work more effectively while delivering the highest quality product within the constraints of the budget.

While Agile teams work well as a unit and are able to react better to the inevitable changes that come with most projects.

4. Why do organizations needs separate testing team and what are the key roles of the tester ?

• Avoid developers perception.
• views/viewpoint
• An independent tester can repeatedly find out more, other, and different defects than a tester working within a programming team – or a tester who is by profession a programmer.

keys roles of tester:

• designing testing scenarios for usability testing.
• responsible for conducting testing and deliver is observations in form of a document to developer team.
•  interact with the clients to better understand the product requirements.

5. what is release note ?

Release notes are documents that are distributed with software products, sometimes when the product is still in the development or test state (e.g., a beta release).

6. when do you do impact analysis and how it helps in improve the quality ?

Even with the most thorough testing, certain features or parts of software can be skipped or tested not sufficiently enough. If the addition of the latest feature introduced bugs in these areas, those bugs would remain undetected. To avoid this situation, software impact analysis should be used.

• Changes are introduced to requirements
• Request for product changes is submitted
• New, planned functionality introduced
• Existing modules and product features are changed

7. challenges faced by testers ?

• Subject awareness
• time
• test estimation
• test data setup
• test automation
• setting up test environment.

8. how do you plan your test case execution?

• Open a detailed view for the Test Plan
• Go to the Runs tab
• Select the Test Plan Run you want to execute.
• Click Run button

When all the Test Steps have been executed, you can select one of 3 run results for the whole Test Case:

• Passed – a test case has been passed successfully
• Failed – there are some issues related to this test case
• Skipped – a test case will be executed later

9. Risk based testing ?

Risk–based testing (RBT) is a type of software testing that functions as an organizational principle used to prioritize the tests of features and functions in software, based on the risk of failure, the function of their importance and likelihood or impact of failure.

10. how to overcome the challenge of not having input documentation for testing ?

Smoke testing is a best option. We identify the functionality and basic and major bugs from that.

Exploratory testing is also a good option. We can find what software does, and does not. The testers have make decisions on what to test next and where to spend more time.

 

 

 

 

PRINCIPLES & TEST TYPES

WEEK 1:

ASSIGNMENT 4:.

1. How do you identify test cases for regression testing ?

It depends on the state of the code and the level we are testing it. In order to identify regression tests, we need to identify part of the program that aren’t expected to change.

Also depends on the company and there environment.

2. how to avoid re-occuring defect ?

By using root cause analysis.

3. How to optimize test cases ?

test optimization is nothing but, quicker pass or fail result, but a reasonably accurate pass or fail.

Run only the tests required to confirm the validity of the changes that triggered the build.

Run all the tests but in an optimal order: any failed tests from the previous build, all tests covering modified code, then in ascending order by test invocation time.

4. How to write reusable test cases ?

1. Identify the vertical markets that your company services — wherever there is more than one client. Examples include banking and e-commerce.

2. brainstorm on a common set of functional and other issues with your team based on the vertical market.

5. difference between alpha and beta testing ?

alpha testing is done in developers site by the testers and developers.

beta testing is done in client site by end users.

6. difference between white and black box testing ?

black box is a method of testing where internal structure or code is not known to the tester. Eg: acceptance testing.

white box is a method of testing where internal code is known to the tester usually the developer does the white box. Eg: unit and integration testing.

7. Difference between functional and nonfunctional testing?

Functional testing is done to make sure that the client and business requirements are met. Eg: positive and negative testing

Non functional testing is done to make sure that system gives a good user experience to the client and end users. Eg: performance/ load testing.

8. Difference between system and integration testing ?

Integration testing is a testing in which individual units or modules are combined and tested as a whole, while system testing is a testing conducted on a complete, integrated system to evaluate the system’s  compliance with its specified requirements. Eg : production environment.

9. difference between smoke and sanity testing?

 Smoke: Software Testing done to ensure that whether the build can be accepted for through software testing or not. Basically, it is done to check the stability of the build received for software testing.

Sanity :After receiving a build with minor changes in the code or functionality, a subset of regression test cases are executed that to check whether it rectified the software bugs or issues and no other software bug is introduced by the changes.

 

 

 

 

 

 

Defect management

Week 1 :

Assignment 3:

1. Why is defect management process important in software development teams ?

Defect management is a means that gives insight in the quality level of the code or documentation that is being tested: the number of defects found during testing and the number of unsolved defects that are remaining in the code (or documentation). Each defect found can be used for process improvement in development teams, what was the reason and how to prevent it.

2. fields in bug report ?

Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005

3. why do defects have priority and severity ?

Defects needs to be categorized based on the priority and severity, so that the developers can work on it as quick as possible and fix it soon.

4. why do defects are deferred ?

deferred defect state means the bug is expected to be fixed in next releases, because impact of bug is not very high and no need to close in same build.

5. how to deal with inconsistent defects ?

We can analyse the bug with the help of application logs. We can attach the log while raising that inconsistent defect along with the screenshots.

6. how do you log a defect ?

• Defect Id
• Priority
• Severity
• Created by
• Created Date
• Assigned to
• Resolved Date
• Resolved By
• Status

7. Defect for high priority and low severity ?

A logo error for any shipment website, can be of low severity as it not going to affect the functionality of the website but can be of high priority as you don’t want any further shipment to proceed with wrong logo.

8. when does the defects gets rejected by the developer ?

• duplicate bug
• wrong test data used
• tester misunderstanding the requirements.

9. what is change request and how can it be handled ?

Change request is noting any changes or alternation in functionality given by the client. If it is within the scope then no problem, if not then we raise the change request. it has to be approved by functional head or ccb (change request control board).

10. how do you do analysis  the root cause of a defect ?

By doing brainstorming on the defect and asking the question ( WHY & WHAT ?)

11. Defect triage ?

process of rebalancing the limited availability of resources for example when there is more defects and less testers, defect are tested based on priority and severity.

 

 

Software testing life cycle

week 1:

Assignment 2:

1. what is the testing process followed in the company ideally  ?

• requirement analysis
• test planning
• test case development
• environment setup
• test execution
• test closure cycle

2. Activities in test design and execution?

test design: testing team writes down the detailed test cases.

test execution: the test cases are executed in this phase.

3. difference between SDLC and STLC ?

SDLC describes the various activities involved in the software development process, whereas STLC describes the activities performed in testing a software.

4. what is test scenario, test condition and test case ?

test scenario: any functionality that can be tested.

test condition: Test Condition is the specification that a tester must follow for testing an Application. There can be multiple Test Conditions in a Test Scenario.

test case : set of actions executed to verify a particular functionality of software is working or not.

5. Process to write a manual test cases ?

• title: include the title of the module your testing
• description : what are you going to test ?
• include assumptions and pre conditions
• keep it very clear and concise.
• expected results
• actual result.

6. what is test cycle why it is important to carry out testing in cycles ?

A Test Cycle is a series of Test Runs to be executed. When creating a Test Cycle, the user selects any or all of the defined groups of Test Cases in the Test Plan.

It is important to carry out testing in cycles because it is a step by step process and each phase has to be completed one by one like a sequence.

7. Explain RTM ?

A document to cover all the user requirements with test cases, should not miss any functionality while testing.

 

 

 

 

 

Software development life cycle

WEEK 1:

ASSIGNMENT 1:

1. Difference between use case and test case ?

use case is a list of action or a event which happens between actor and system.

test case is a set of conditions in which the tester will determine whether the software or its features is working or not as established in the requirement analysis.

2. which phase of the SDLC does the tester begins to write the test cases ?

Mostly when the requirement specification is completed, tester can write test cases parallel to the design phase itself.

3. Difference between functional document and business document ?

business document describes the high level business needs.

Functional document describes the functions required to fulfill the business needs.

4. who are the different stakeholders involved in different phases of the SDLC

1. Requirements– Business Analyst
2. Design – System Architect
3. Coding – Software Developer /  Development Team
4. Testing – Tester / Testing Team
5. Implementation – Operational Team
6. Maintenance – Production Support Team
   

5. why do we need a separate environment for developers and testers ?

First purpose is to run the software as it is used by the client side itself.

second purpose to have the test environment separate to development environment is to restrict developer’s intervention (hide) in test environment during the test phase. This is to be done so that the test results are clear, real and non-ambiguous.

6. role of business analyst in phase of SDLC ?

Initiating, planning, monitoring and control and closing the phases.

7. role of developer in SDLC ?

• Analyze Database Design
• Coding and unit testing on Localhost

8. role of tester in SDLC ?

• Functional/Integrated Testing (not developer)
• writing test cases.

9. role of customer in SDLC ?

• involved in defining the requirements and testing phase (user acceptance testing) beta testing

 

 

KMS, Knowledge Management Systems

Hey guys this week we are going to discuss about knowledge management systems and its issues.

An evolution of information system, when KM first developed in 15 years, information management is the biggest push to KM. The technology point is very strong in KMS and also technology approach to KM.

KMS supports KM with tacit and explicit knowledge (captured or codified in a system). If you call your explicit knowledge, you also put that in a KMS. A really KM will capture the tacit knowledge ( it is hard to bring it outside of a person).

Technological system might capture tacit knowledge. For example neuro links (what happens when you connected to a Personal computer ? ). Another way to capture tacit knowledge is narrative database, video taping (explaining in local language), pictures and drawings.

In the chess game the PC captures the moves of real people do (it knows what are the possible moves). Other way of gaining knowledge is Brainstorming as group.

LEVEL OF KNOWLEDGE MANAGEMENT 

Knowledge management system is a system which focus mainly on issues in organisation. KMS improves efficiency and adoption of knowledge among employees who are working in an organisation.  This system creates a systematic process of capturing information which helps the organisation.

Information system on the other hand is a combination of hardware, telecommunication networks and software which helps employees capture and collect information useful for organizations.

Key Elements of information system 

 I think KMS is a tool or a system that stores and retrieves, knowledge and information. With knowledge and information on your system, an organization can perform well. 

One of the main role of KMS is to help employees in organization learn about knowledge by sharing. KMS takes into account all issues in organization from strategic to operational. KMS can convert information to knowledge using the KMS tools.

A well organized KMS can help organization increase profit, staff performance, client satisfaction and increase the quality of service. With KMS in your company each and every employee has been given access to knowledge and management rules.

Technology keeps on updating and people need to be aware of all new technology updates especially IT people, so KMS helps you captures those updates for future use.

Roles of KMS 

 

Organisational Learning, Business Intelligence, Information Management, Analytics and Big Data

Week 5:

Hey guys this week we are going to discuss about Analytics, Big Data, Business Intelligence and how they are related to Knowledge Management.

From my understanding, analytics is like gathering data and converting them into information especially for business needs using the customer details. We can use information systems to capture this information and use them for future investment.

The main objective of analytics is to improve the business of an organisation by gaining data or information to increase the profit.

Evolution of Analytics

From the following diagram, we can see the evolution of analytics.

Big Data is the use of analytics method that extract value from data or information used to improve business. It involves capturing, storing, updating and visualization of information, so that the large amount of data is arranged in an order.

The aim of the big data is to solve customer related issues; it may be old or new.

There are four V’s of big data, they are volume, velocity, variety and veracity.

Big Data increases the storage, processing power, and availability of data. Big data is applied in many fields and uses NoSQL as one of its technologies. Facebook, google, eBay where the first to implement Big data which helped to reduce cost reductions.

Big Data sources

Business Intelligence:

BI uses tools to capture big data, which is turned into information and can be displayed on the screen. BI technologies provide predictive view of operating a business. The main goal of BI is to create new strategic business opportunities based on big data to have competitive advantage over market.

H.J. Watson gives an example of how the competitive element can act as an incentive. In a call centre a performance dashboard monitors each call made by the agents and lists them based on the performance metrics. So, each agent can see their performance with others and can see where each of them stand. This helped to improve agent’s performance.

Organisational Learning:

How people create knowledge to make their employee become smarter and creative. For example, you are the CEO of an organisation, if everything is split, how you put everything to make your organisation work well.

Information Management:   

This focus on data and information, greatly on technology based because it can easily have codified and transferred to those who need it the most. It involves planning, organising, structuring, reporting of information activities.

Personal knowledge management

 

Week 3:

Hey guys,

This week we will discuss about personal knowledge management and how it differs from knowledge management.

Dave Snowden “We always know more than we can say and we always say more than we can write”.

Personal knowledge management (PKM) “is a collection of processes that a person uses to gather, classify, store, search, retrieve and share knowledge in their daily activities” (Grundspenkis 2007).

This set of processes helps use to understand the world and work with them more effectively.

PKM means taking control of your professional development, and staying connected in the network era, whether you are an employee or self-employed.

PKM is a bottom-up approach to knowledge management (pollard 2008).

PKM focuses more on individual skills or ideas to knowledge management than organisational one.

The main goal of PKM is to make people highly skilful or knowledgeable in their life.

It is up to the individual who uses the PKM to his advantage. PKM can also be used as a tool to manage individual skills to organisational benefit through sharing their ideas in both short and long term.

It can be also considered as a set of skills an individual or an employee must learn to gain competitive advantage or perform a specific task in an organisation.

See you guys next week with another important topic.

 

 

 

 

Knowledge Management

Week 3

Hey guys,

This week we will discuss about knowledge management and its key issues.

Knowledge Management, (KM) is a concept and a term that arose approximately two decades ago, roughly in 1990.

Davenport (1994) defined knowledge management as “is the process of capturing, distributing, and effectively using knowledge”.

Duhon, 1998 gave another definition for knowledge management as “Knowledge management is a discipline that promotes an integrated approach to identifying, capturing, evaluating, retrieving, and sharing all an enterprise’s information assets”.

KM is taught in many field such as information systems, information science, management, library and business administration and used as research topic in computer science and information media.

KM involves data mining and some method of operation to push information to users.

 

 

“Jeff Angus and Jeetu Patel” describe a four-process view of knowledge management that we have put into a table

This major process…	Includes these activities….
Gathering	Data entry OCR and scanning Voice input Pulling information from various sources Searching for information to include
Organizing	Cataloging Indexing Filtering Linking
Refining	Contextualizing Collaborating Compacting Projecting Mining
Disseminating	Flow Sharing Alert Push

 

Knowledge management offers organisations an array of business benefits.

Following quote explains it “A firm’s competitive advantage depends more than anything on its knowledge: on what it knows – how it uses what it knows – and how fast it can know something new”.

This quote explains link between knowledge management and a competitive advantage.

 

Evolution of Knowledge Management

Additional motives driving the need for Knowledge Management, include:

• KM supports establishment to share valuable visions
• Hold intellectual investment when staffs resign
• Better adjust to varying situations and marketplaces
• Globalization needs establishments to share information across nations
• Decrease training time for workers

KM is used in supporting, distribution and integration of information. Knowledge management discourses the living knowledge inside the company, from tactical to decision-making and operational level. In other words, KM has all the essential gears to help business representatives turn information into knowledge.

Benefits of knowledge management within an organization are

• All the Staff members of the organization has access to management and business knowledge
• It is easy to backup new technologies and capture new information for upcoming use
• Because of the prevailing knowledge base, the staff members can access all the information and data they need any time
• Produce knowledge base articles by means of the real-time HTML editing tools
• Enables IT employees to stay in update with the latest new technologies
• Decreases IT prices without having to concession excellence facility to internal and external customers
• Advances employees meeting and communication
• Assists employees in bringing better quantity and liability

When interviewed managers, their key anxieties about knowledge management, they expressed concern mainly over the cultural, managerial and informational issues.

When it comes to culture, the managers were worried over the implications for change of management, the skill to influence staff members to transfer their skills, and the capability to convince corporate units to share their ideas with other organisation, mostly when each corporate unit was responsible for display a revenue.

The managerial concerns associated to the commercial value of knowledge management and the necessity for metrics upon which to prove the value. There was anxiety about determining who would be responsible for managing the knowledge.

Key issues in knowledge management: