The test case is defined as a group of conditions under which a tester

determines whether a software application is working as per the customer's

requirements or not. Test case designing includes preconditions, case name,
input conditions, and expected result. A test case is a first level action and
derived from test scenarios.

We will write the test case when we get the following:

● When the customer gives the business needs then, the developer

starts developing and says that they need 3.5 months to build this

product.

● And In the meantime, the testing team will start writing the test cases.

● Once it is done, it will send it to the Test Lead for the review process.

● And when the developers finish developing the product, it is handed

over to the testing team.

● The test engineers never look at the requirement while testing the

product document because testing is constant and does not depends

on the mood of the person rather than the quality of the test engineer.
Penetration testing (or pen testing) is a security exercise where a
cyber-security expert attempts to find and exploit vulnerabilities in a

computer system. The purpose of this simulated attack is to identify any

weak spots in a system's defenses which attackers could take advantage of.

The Five stages of Penetration Testing

There are five penetration testing phases: reconnaissance, scanning,

vulnerability assessment, exploitation, and reporting.

Reconnaissance

The first penetration testing phase is reconnaissance. In this phase, the tester gathers as

much information about the target system as they can, including information about the

network topology, operating systems and applications, user accounts, and other relevant

information. The goal is to gather as much data as possible so that the tester can plan an

effective attack strategy.

Scanning

Once all the relevant data has been gathered in the reconnaissance phase, it’s time to

move on to scanning. In this penetration testing phase, the tester uses various tools to

identify open ports and check network traffic on the target system. Because open ports are

potential entry points for attackers,

Vulnerability Assessment
The third penetration testing phase is vulnerability assessment, in which the

tester uses all the data gathered in the reconnaissance and scanning phases

to identify potential vulnerabilities and determine whether they can be

exploited. Much like scanning, vulnerability assessment is a useful tool on its

own but is more powerful when combined with the other penetration testing

phases.

Exploitation

Once vulnerabilities have been identified, it’s time for exploitation. In this

penetration testing phase, the penetration tester attempts to access the

target system and exploit the identified vulnerabilities, typically by using a

tool like Metasploit to simulate real-world attacks.

Reporting
Once the exploitation phase is complete, the tester prepares a report
documenting the penetration test’s findings. The report generated in this
final penetration testing phase can be used to fix any vulnerabilities found in
the system and improve the organization’s security posture.

Test case component.

Test Case ID

Test Case Description

Pre-Conditions

Test Steps

Test Data
Expected Result

Post Conditions

Actual Result

Status

Agile Software Development is an iterative and incremental approach to software

development that emphasizes the importance of delivering a working product quickly
and frequently. It involves close collaboration between the development team and the
customer to ensure that the product meets their needs and expectations.

What is agile planning?

Agile planning is an iterative approach to managing projects avoiding the traditional concept
of detailed project planning with a fixed date and scope. Based on the principles rooted in
the Agile Manifesto, Agile project planning emphasizes frequent value delivery, constant
end-user feedback, cross-functional collaboration, and continuous improvement.
Unlike traditional project planning, Agile planning remains flexible and adaptable to changes
that may emerge at any project lifecycle stage.
An agile project plan is divided into releases and sprints
Agile planners define a release as creating a new product or substantially updating an
existing product. Each release is broken down into several iterations called sprints.
Each sprint has a fixed length, typically two weeks, and the team has a predefined list of
items to work through in each sprint. The work items are called user stories.

Planning is based on user stories

As mentioned above, a user story is an item that caters to users’ needs. For
example:

“As a team member, I need to know which tasks are currently assigned to
me.”
“As a team leader, I need to receive an email notification when a task is
stuck or behind schedule.”
Unlike in traditional project management methodologies like waterfall, in
which teams would create detailed technical specifications of exactly what
they would build, in agile planning, the team only documents what the user
needs.

Planning is iterative and incremental

An iterative process allows the team to learn what they are capable of,
estimate how many stories they can complete in a given timeframe, and
discover problems that impede their progress. These problems can be taken
care of in subsequent sprints.

Estimation is done by team members themselves

A core ethic of agile planning is that development teams should participate in planning
and estimation, instead of management deciding on the work scope. In this spirit stage,
agile planning allows teams to determine the complexity of user stories to carry out a
plan. In agile methodology, the process of defining work complexity is called a story
point.

principles of agile