Forem: AKTHER HAMID SAYMON

Overview of the test case component & bug report in Software Testing

AKTHER HAMID SAYMON — Tue, 08 Jun 2021 13:27:30 +0000

What is Test Case?
A test case is a document that describes an input, action, or event, and its expected results, in order to determine if a feature of an application is working correctly.

A test case (how to test) is a document which consists of a set of conditions or actions which are performed on the software application in order to verify the expected functionality of the feature.

Some elements of Test Case:

Test Suite ID: The ID of the test suite to which this test case belongs.
Test Case ID: The ID of the test case.
Test Scenario: A Test Scenario is defined as any functionality that can be tested. It is a collective set of test cases .
Test Procedure(Test Steps): Step-by-step procedure to execute the test.
Test Data: The test data, or links to the test data, that are to be used while conducting the test.
Expected Result: The expected result of the test.
Actual Result: The actual result of the test; to be filled after executing the test.
Status(Pass/Fail): After comparing with both expected result & actual result the tester( creator of test case) evaluate weather the test case is Pass/Fail.

What is Bug Report?
A Bug Report in Software Testing is a detailed document about bugs found in the software application. Bug report contains each detail about bugs like description, date when bug was found, name of tester who found it, name of developer who fixed it, etc. Bug report helps to identify similar bugs in future so it can be avoided.

The key elements of a bug report in Software Testing:

Title: An appropriate title is simple, brief, and provides a description of what the bug is to the developer.
Description: This is a description, written in brief, of the bug and how and why it happened. More specifics than the title should be included in this part.
Reproducing steps: This must include the maximum steps required for the bug to repeat. The steps should ideally be brief, quick, and everyone can follow them.
Environment: This section should provide all the specifics of the setup and configuration of the environment that the app is running on.
Expected Result: This is the result of an activity that was anticipated or expected.
Actual Result: This is the result observed by the tester or user.
Attachments: Attachments can be very useful for the developer to recognize the problem faster.
Severity and Priority: Severity and Priority is a measure of how important and how serious an issue is.
Assignee: To whom the bug is allocated.

Overview of the test plan in manual testing

AKTHER HAMID SAYMON — Tue, 08 Jun 2021 12:22:41 +0000

What is Test Plan?
A project's test plan is a document that is created at the project level. It dictates which work items will be tested, how they will be tested, and how test types will be distributed among testers.

A test plan is a document that describes a software testing effort's scope, approach, objectives, resources, and schedule.
It's the document that defines out a testing project's what, when, how, and who.

Activities for Test Planning:

To define the scope and dangers that must be examined, as well as those that must not be examined.
Creating a Test Strategy Document
Taking a look at the test estimate.
Planning when and how to test, selecting how to evaluate test results, and setting a test exit criterion.

Test Plan components:

Test plan identifier: Unique identifying reference.
Introduction: A brief overview of the project as well as the document.
Test items: A test item is a software program that represents the application being tested.
Features to be tested: A feature that needs to be tested on the software.
Features not to be tested: Identify the features and the reasons why they were not included in the testing.
Approach: Details on the overall testing strategy.
Item pass/fail criteria: Everything was documented whether a software program passed or failed its test.
Test deliverables: Test plans, test specifications, and test summary reports are examples of deliverables that are delivered as part of the testing process.
Test Environment: Defining the environment's requirements, including hardware, software, operating systems, network setups, and tools.
Responsibilities: Lists the team members' duties and responsibilities.
Staffing and training needs: The actual workforce requirements, as well as any specialized skills and training requirements, are captured.
Schedule: Indicates major project deadlines and critical milestones.
Risks and Mitigation: High-level project risks and assumptions, as well as a plan to reduce each risk.
Approvals: All document evaluated and the results, their titles, and the sign-off date are recorded.

Types of Document in Software Testing

AKTHER HAMID SAYMON — Tue, 08 Jun 2021 09:25:54 +0000

Types of Document in Software Testing:

Test Plan
Test Scenario
Test case
Traceability Matrix

Test Plan:
Test Plan is a document prepared at the project level. It determines the work products to be tested, how they will be tested, and the distribution of test types among testers in general.

A Test plan is a document describing the scope, approach, objectives, resources, and schedule of a software testing effort.
It is the document that outlines the what, when, how, who more of a testing project.

Test Scenario:
A Test Scenario is a single-line statement that specifies the area in which your application will be tested.

A TEST SCENARIO (What to test) is defined as any functionality that can be tested. It is also called Test Condition or Test Possibility.

As a tester, you should put yourself in the end user’s shoes and figure out the real-world scenarios and use cases of the Application Under Test.

Test case:
A test case is a document that describes an input, action, or event, and its expected results, in order to determine if a feature of an application is working correctly.

Traceability Matrix:
The Traceability Matrix, also known as the Requirement Traceability Matrix (RTM), is a table used to track requirements in the Software Development Life Cycle (SDLC).

What are the Feature Driven Development Process?

AKTHER HAMID SAYMON — Mon, 01 Mar 2021 06:21:47 +0000

Feature Driven Development Process is consist of five-phase, those are:
1. Develop an Overall Model.
2. Build a Features List.
3. Plan By Feature.
4. Design By Feature.
5. Build By Feature.

Process 1: Develop an Overall Model:
Make a modeling group. Build a high-level object model by walking around the domain. Keep a log of your thoughts.
The goal is for team members to establish a strong understanding of the problem domain and lay a solid foundation.

Process 2: Build a Features List:
All features are grouped into three levels: Domain Subject Area, Business Activity, Features.

Process 3: Plan By Feature:
Make an initial schedule: Developed at the level of individual characteristics based on prioritizing based on business value.
Consider the following factors: dependencies, difficulty, and risks.
Assign duties to members of the team: Identify the Class Owners, Chief programmers should be assigned feature sets.

Process 4: Design By Feature:
Create Featured Teams. Members of the teamwork together on the entire low-level analysis and design.
Certain features may necessitate the involvement of domain experts. To support their changes, teams must update the model artifact.

Process 5: Build By Feature:
Implement the feature that you've planned. Unit-level and feature-level testing.
Inspections of the building code are required. Integrate with the standard build process.

Feature Driven Development in SDLC, Feature Driven Development Roles.

AKTHER HAMID SAYMON — Wed, 10 Feb 2021 05:25:56 +0000

What is Feature Driven Development?

FDD is an agile software development process. FDD uses a short-iteration model. Along with other industry-recognized best practices, FDD combines key benefits of other common agile methods. To easily scale to much larger projects and teams, FDD was developed.

What is a Feature?

Limited function explained in terms valued by the customer. FDD's user requirements form. The characteristics are "small" in the sense that it will take no more than two weeks to complete them.
Characteristics that seem to take longer are to be broken up into a series of smaller characteristics.
Note: The limit is two weeks, with most features taking far less time (1 - 5 days).

Feature naming template:
Action + the result + by/for/of/to + a(n) + object.

Examples:

Calculate the total of a sale.
Validate the password of a user.
Authorize the sales transaction of a customer.

Feature Driven Development Roles:

Class Ownership: Class owner allocated to a particular developer. Class owner responsible for all modifications to new features implementation.

Collective Ownership: Any developer can change any artifact at any moment, solving the deadlock issue. Class Ownership does not mean exclusivity, nor liability alone.

FDD Primary Roles:
Project Manager, Chief Architect, Development Manager, Domain Experts, Class Owners, Chief Programmers.

FDD Supporting Roles:
Domain Manager, Release Manager, Build Engineer, System Administrator, Tester, Deployer, Technical Writer.

Dynamic Software Development Method (DSDM) in SDLC, DSDM Phases, DSDM Techniques.

AKTHER HAMID SAYMON — Thu, 04 Feb 2021 07:53:58 +0000

What is the Dynamic Software Development Method(DSDM)?

DSDM is an approach to software development for Rapid Application Development (RAD) which offers an agile platform for project delivery. The key feature of DSDM is that users need to be actively involved, and the decision-making power is provided to the teams.

DSDM Phase-

Pre-Project Phase:
You make sure the projects are set up based on a specific target during the Pre-Project process. To begin the feasibility stage of the project, you must ensure that resources exist.

Feasibility Phase:
You want to make sure projects are technologically feasible and cost-effective during the feasibility process. You do only enough to decide whether the priorities of the company are appropriate for further preparation.

Foundations Phase:
The aim here is to get a picture of the project's scope of work and place the basis for identifying it and estimating the completion of items within the project, using range estimates if appropriate.

Evolutionary Development Phase:
To control the iterations, Evolutionary Creation makes use of timeboxing, with each iteration releasing a completed piece of a much larger whole.

Deployment Phase:
In many cases, you can either deploy the entire solution, which might make sense, or with each loop, you can deploy small parts of the solution through an iteration of evolutionary growth.

Post-Project Phase:
Your project is complete and you reach the Post-Project Phase when all of your prototypes are complete and you have a solution or product completely created.

DSDM techniques-

Flexibility: The flexibility of the criteria to be achieved has a direct effect on the processes and controls of implementation and on system acceptance.
It assumes that 80% of the proposed system can be generated in 20% of the time it would take to create the entire system, which is useful and useful.

80:20 Model: A basic principle is that nothing is constructed completely for the first time, but that 80% of the proposed method can be generated in 20% of the time it would take to create the complete solution in a functional and useful way.

Time Boxing: In addition to the activities that lead to its execution, Timeboxing operates by focusing on when a business target will be reached.

MoSCoW Rules:
Must have – fundamental to project success.
Should have – important but the project does not rely on.
Could have – left out without impacting on project.
Want to have but Won't have this time for those valuable requirements that can wait till later development takes place.

Sprint in Scrum Methodology, Sprint workflow and process.

AKTHER HAMID SAYMON — Sun, 31 Jan 2021 12:43:01 +0000

What is the Sprint?

Sprints are iterative cycles where to produce new increments, the functionality is developed or enhanced. Sprint Planning Meetings, Sprint Backlog, and Daily Scrum meetings are the team's operating tools.
It is planned that one Sprint will last from one week to one month.

Sprint workflow and process:

Sprint Planning meeting: A two-phase meeting organized by the Scrum Master is a Sprint Planning Meeting. In the first phase of the meeting, the customers, users, management, product owner, and Scrum Team participate in deciding on the objectives and functions of the next Sprint. The Scrum Master and the Scrum Team will hold the second phase of the meeting focusing on how the production increase will be implemented during the Sprint.

Sprint Backlog: The starting point for each sprint is the Sprint Backlog. This is a list of selected products for the Product Backlog to be introduced in the next Sprint. In the Sprint Planning Meeting, the items are chosen by the Scrum Team along with the Scrum Master and the Product Owner on the basis of the prioritized items and priorities set for the Sprint.
The Sprint Backlog is stable before the Sprint (i.e. 30 days) is finished, as opposed to the Product Backlog. A new version of the method is delivered when all the things in the Sprint Backlog are done.

Daily Scrum meeting: To keep track of the progress of the Scrum Team constantly, regular Scrum meetings are scheduled and they also act as planning meetings: what has been done since the last meeting and what needs to be done before the next one. In this short meeting (approximately 15 minutes) held daily, issues and other variable issues are also addressed and regulated. Scrum meetings are run by the Scrum Master.

Sprint Review meeting: On the last day of the Sprint, in an informal meeting, the Scrum Team and the Scrum Master introduce the results of the Sprint to the management, clients, users, and the Product Owner. The participants analyze the rise in the commodity and make the decision on the following operations. New backlog things may be brought out at the review meeting and also alter the course of the system being designed.

Scrum in Agile Methodology, Scrum Process, Roles and responsibilities in Scrum.

AKTHER HAMID SAYMON — Fri, 29 Jan 2021 16:58:12 +0000

What Is the Scrum?

SCRUM is an agile method of development that focuses primarily on how to handle activities within a team-based system of development. Scrum is literally derived from the action that happens during a rugby match.

Scrum process includes three phases:
Pre-Game:
Two sub-phases are included in the pre-game stage:

Planning: Description of the software that is being developed. A list of Product Backlogs is generated including all the currently known specifications.
The requirements are prioritized and the effort necessary for their execution is estimated. With new and more specific items, as well as more specific estimates and new priority requests, the Product Backlog list is continually updated.

Architecture: Based on the current items in the Product Backlog, the high-level design of the system, including the architecture, is scheduled.
In the case of an update to an existing system, the modifications necessary to introduce the backlog items are listed along with the issues they may cause. A design review meeting is held to review implementation plans and decisions are taken on the basis of that review.

Development phase (Game phase):

This stage is regarded as a "black box" where it is supposed to be unpredictable. In Sprints, the system is built.

Post game:
When an agreement has been reached that the environmental variables such as the requirements are completed, this stage is entered into.
No more things and problems can be found in this case. The system is now ready for release and during the post-game stage, including activities such as integration, system testing, and documentation, planning for this is being done.

Roles and responsibilities:

Scrum Master: The Scrum Master is responsible for ensuring that the project is managed in accordance with Scrum's practices, principles and rules and that it proceeds as expected. During the project, Scrum Master communicates with the project team as well as with the client and the management.

Product Owner: The project, management, monitoring, and control of the Product Backlog list is officially the responsibility of the Product Owner. The Scrum Master, the customer, and the management pick him. He makes the final decisions on the tasks relating to the Backlog product.

Scrum Team: The Scrum Team is the project team that has the ability to decide on the actions required and to coordinate itself in order to achieve each Sprint's objectives.

Customer: For the system being built or improved, the consumer participates in the activities related to product backlog products.

Management: Management, along with the charters, rules, and conventions to be observed in the project, is in charge of final decision making. In the setting of goals and criteria, management frequently participates.

Extreme Programming (XP) in SDLC, Phases of Extreme Programming (XP).

AKTHER HAMID SAYMON — Mon, 25 Jan 2021 18:58:23 +0000

What is the Extreme Programming (XP)?
Extreme Programming (XP) is an agile method for software development that aims to produce software of higher quality and to increase the development team's quality of life.

The life cycle of XP consists of five phases:

Exploration.
Planning.
Iterations to Release.
Productionizing.
Maintenance and Death.

Exploration:
The clients write out the story cards that they want in the first release to be included. Around the same time, the project team is familiar with the methods, technologies, and activities they are going to use in the project.
Depending mostly on how familiar the technology is to the programmers, the exploration phase takes from a few weeks to a few months.

Planning:
Its primary role is to set targets and some iterative cycles for the entire project. His vision of the product is customer tales, formulated by the client. In the release schedule, the developers estimate and prioritize them. The work on translating them into tasks starts after that.

Iterations to Release:
Includes several iterations of the systems before the first release. Each takes one to four weeks to implement. The first iteration creates a system with the architecture of the whole system.
This is achieved by selecting the stories that will enforce building the structure for the whole system. The customer decides the stories to be selected for each iteration.
At the end of the last iteration, the system is ready for production.

Productionizing:
It needs further testing and checking of the system's output before the system can be released to the client. New improvements can still be found, even if they are included in the latest version, the decision has to be taken.

Maintenance and Death:

Maintenance Phase: The XP project must both keep the system running in development after the first release is produced for user use, while still developing new iterations.

Death phase: If the client does not have any stories to be introduced anymore. In other ways, the device also meets consumer requirements.

Agile Methodology, Four Core Concept of Agile Methodology, Agile Manifesto.

AKTHER HAMID SAYMON — Thu, 21 Jan 2021 10:34:46 +0000

What Is Agile Methodology?
The Agile SDLC model is a mix of iterative and incremental process models focused on process adaptability and customer satisfaction through the rapid delivery of the product with working software. Usually, each iteration lasts from about one to four weeks.

Four Core Concept of Agile Methodology:

Interactions between individuals and teams over tools and procedures.
Working software on detailed documentation.
Customer cooperation in negotiating contracts.
Responding to change according to a project.

Agile manifesto:

Our highest priority is to please the client by providing useful applications early and consistently.
Welcome changing demands, even late in creation. Agile method harness adjustment for the strategic benefit of the customer
Deliver working applications regularly, with a preference for the shorter time scale, from a few weeks to a few months.
Throughout the project, business people and developers must work together daily.
Create projects around people who are inspired. Offer them the atmosphere and support their needs, and trust them to do the job.
Face-to-face conversation is the most powerful and productive way of communicating information to and inside a production team.
The important aspect of development is working software.
Agile methods encourage sustainable development. It should be possible for sponsors, developers, and users to maintain a steady speed indefinitely.
Agility is improved by a constant commitment to technological quality and good design.
It is important to have simplicity-the art of minimizing the amount of work not completed.
From self-organizing teams, the best architectures, specifications, and prototypes emerge.
The team focuses on how to become more productive at regular intervals, then tunes and modifies its actions accordingly.

Agile Methodology Example:
-->Scrum.
-->Extreme Programming (XP).
-->Dynamic Systems Development Method (DSDM).
-->Crystal Methods.
-->Feature-Driven Development (FDD).
-->Lean Development (LD).
-->Adaptive Software Development (ASD).

Some of the most popular Software Development Life Cycle (SDLC) models.

AKTHER HAMID SAYMON — Mon, 18 Jan 2021 12:00:15 +0000

Waterfall Model:
The waterfall model is a sequential model that divides software development into pre-defined phases. Each phase must be completed before the next phase can begin with no overlap between the phases.
Those phases are Communication, Planning, Modeling, Construction, Deployment. The waterfall model is used when all the requirement is clear.

Agile Model:
The Agile SDLC model is a mix of iterative and incremental process models focused on process adaptability and customer satisfaction through the rapid delivery of the product with working software. Usually, each iteration lasts from about one to four weeks.
Some of those models are Scrum, Dynamic Systems Development Method (DSDM), Crystal Methods, Feature-Driven Development (FDD), Lean Development (LD), Extreme Programming (XP), Adaptive Software Development (ASD).

Prototyping Model:
The prototyping model is a software development model in which a prototype is built, tested, and reworked until an acceptable prototype is achieved. It used when requirements are not clear.

Spiral Model:
The process is portrayed as a spiral rather than a series of backtracking activities. In the phase, each loop in the spiral represents a stage. No set stages, such as design or specification.

Incremental Model:
Incremental Model is a process of software development where requirements divided into multiple standalone modules of the software development cycle.

V-Model:
The phase is arranged in parallel with this type of SDLC model testing and development. There are therefore verification steps on the side of SDLC and on the other side of the validation process. The V-Model is joined by the coding phase.

Software Development Life Cycle (SDLC), SDLC PHASES, Importance of SDLC

AKTHER HAMID SAYMON — Thu, 14 Jan 2021 11:11:41 +0000

What is Software Development Life Cycle (SDLC)?

Software Development Life Cycle (SDLC) is a structured software development process that ensures the value and correctness of the built software.

SDLC Phases-
The SDLC process divided into the following phases:

Phase 1:
Requirement Analysis: Communicating to collect and document project specifications with stakeholders and users. This phase contain requirements gathering, project initiation, estimating, scheduling, tracking, SRS documentation.

Phase 2:
Design: Building a software system architecture and element based on software requirements specification (SRS) Document. This phase contain mainly system architecture.

Phase 3:
Coding: Development of the software by the development team using a programming language.

Phase 4:
Testing: The software developed is thoroughly tested and any bugs found are assigned to developers to fix them.

Phase 5:
Deployment: After the product is tested, the production team preparing the software to run and live in a specific environment.

Phase 6:
Maintenance: The product is updated and maintained after it has been introduced to the market.

Importance of the SDLC for developing a software system:

It provides a framework for planning, scheduling, and estimating projects.
It provides a basis for a standard collection of projects and deliverables.
It is a tool to manage and control projects.
It increases project development visibility for all interested.
It stakeholders in the construction phase.
It increased and boosted the speed of development.
It improved connections with clients.
It allows you to reduce project risk and efficiency plan for project management.