1.

What are the automation challenges that SQA (Software

Quality Assurance) team faces while testing?
As the software quality assurance landscape is rapidly growing and facing significant
changes, QA and testing professionals are facing new challenges related to better
understanding, managing, and adopting different types of QA testing

Today, development cycles have become quick and short and both of these have contributed
to changes in the software quality assurance definition. It now mainly encompasses keeping
pace with the market without compromising on the product quality. Enhanced software
quality assurance activities provide several benefits including optimization, quality, process
improvement as well as higher productivity..

1. Facilitation of Quality
Understanding the nature of business is immensely important for a system being verified.
Hence, QA and testing professionals need to join hands with product owners to be able to test
a product in such a manner that it properly supports the business model.

QA teams should be able to be involved in the initial discussions that would help them to act
as facilitators of quality.

2. QA Culture
When it comes to performing software quality assurance activities seamlessly, the QA and
testing culture needs to undergo a change. Organizations now need to explore innovative
ideas to find unique techniques together with different QA testing tools both of which would
contribute in testing a product efficiently and quickly. This will also help the organizations to
ensure a continuous balance between meeting market demand with a high-quality end
product.

3. Early Testing
Like development engineers, QA and testing professionals are extremely important in an
SDLC. If testing begins at the early stages of the development cycle, they can visualize
different quality issues throughout the entire cycle and provide valuable early feedbacks on
sustainable development, feature, scope, and architecture, all of which can greatly contribute
to reduce unnecessary delay in time-to-market and high amount of additional expenses
arising out of late detection of errors.

4. Merge Development With Testing

To build an effective development team, organizations need to mix the development teams
with software quality assurance teams in terms of knowledge sharing. That being said, QA
and testing professionals should be encouraged to have some knowledge about the
development process of a product while the developers should be encouraged to take active
parts in enhancing test automation infrastructure and should possess knowledge about
different QA testing tools.

Finally, an efficient testing strategy should comprise of different types of QA testing that
include manual, automated and exploratory testing. All of these contribute to effectively
tighten the release cycles and lower risks. Three types of QA testing have to be included in a
robust testing strategy.
 2. Java Program to check if Number is vowel or consonant

1. class Char
2. {
3. public static void main(String[ ] arg)
4. {
5. int i=0;
6. Scanner sc=new Scanner(System.in);
7. System.out.println("Enter a character : ");
8. char ch=sc.next( ).charAt(0);
9. if(ch=='a'||ch=='e'||ch=='i'||ch=='o'||ch=='u'||ch=='A'||ch=='E'||ch=='I'||ch=='O'||
ch=='U')
10. {
11. System.out.println("Entered character "+ch+" is  Vowel");
12. }
13. else if((ch>='a'&&ch<='z')||(ch>='A'&&ch<='Z'))
14. System.out.println("Entered character "+ch+" is Consonant");
15.       else
16. System.out.println("Not an alphabet");
}
}

3.Java Program to check if Number is Positive or Negative

public class Demo

{
public static void main(String[] args)
{
int number=109;
if(number > 0)
{
System.out.println(number+" is a positive number");
}
else if(number < 0)
{
System.out.println(number+" is a negative number");
}
else
 {
System.out.println(number+" is neither positive nor negative");
}
}
}

4.How to collect software requirement

1. Establish Project Goals and Objectives Early

This step can feel redundant: of course we know why we’re doing this project…

Even if we think we know, write it down, and get our stakeholders   to sign off on it. Without
clearly stated goals and objectives, we are lacking a framework to guide future decision-
making.

2. Document Every Requirements Elicitation Activity

When we are in the midst of stakeholder interviews and documentation review, we can often
feel like we have a great grasp on things. But then a week goes by, and some details start to
get a little fuzzy, and we realize we don’t quite have a full grasp of our business
requirements. It sounds obvious.

3. Be Transparent with Requirements Documentation

Sure, we understand the requirements. And our stakeholders  understand the requirements.
But do our stakeholders understand our understanding of the requirements

After every meeting, go through our notes and clean them up – then share them with the

4. Don’t Make Assumptions About Requirements

Don’t assume that we understand everything, even if it seems obvious. A seemingly simple
requirement even.

5. Confirm, Confirm, Confirm

. Just sharing our notes with a stakeholder is great, but far more valuable is actually having a
quick review with them and getting their official sign-off. This is true for meeting notes, user
stories, diagrams, wireframes, really any kind of requirements artifact that we are creating.

6. Focus On Business Requirements, Not Tools

Be careful when gathering requirements that we are really focusing on and listening to what
our stakeholder needs, not what our tool-of-choice happens to do best.
 Listen and gather first, then determine where the gaps are between our stakeholder’s needs
and any existing product.

5.What is inheitence in java..

Inheritance can be defined as the process where one class acquires the properties
(methods and fields) of another. With the use of inheritance the information is made
manageable in a hierarchical order.
The class which inherits the properties of other is known as subclass (derivedclass, child
class) and the class whose properties are inherited is known as superclass (base class,
parent class).

extends Keyword

extends is the keyword used to inherit the properties of a class. Following is the
syntax of extends keyword.
Syntax
class Super {
.....
.....
}
class Sub extends Super {
.....
.....}
What are the main concept of oops in java

6.Definition of OOP Concepts in Java

OOP concepts in Java are the main ideas behind Java’s Object Oriented Programming.

They are an abstraction, encapsulation, inheritance, and polymorphism.

Basically, Java OOP concepts let us create working methods and variables, then re-use all or
part of them without compromising security.

List of OOP Concepts in Java

There are four main OOP concepts in Java. These are:

 Abstraction.

 Abstraction means using simple things to represent complexity. We all know how to turn
the TV on, but we don’t need to know how it works in order to enjoy it. In Java,
abstraction means simple things like objects, classes, and variables represent more
complex underlying code and data.

 Encapsulation. This is the practice of keeping fields within a class private, then

providing access to them via public methods. It’s a protective barrier that keeps the data
and code safe within the class itself. This way, we can re-use objects like code
components or variables without allowing open access to the data system-wide.

 Inheritance. This is a special feature of Object Oriented Programming in Java. It lets

programmers create new classes that share some of the attributes of existing classes. This
lets us build on previous work without reinventing the wheel.

 Polymorphism. This Java OOP concept lets programmers use the same word to mean
different things in different contexts. One form of polymorphism in Java is method
overloading. That’s when different meanings are implied by the code itself. The other
form is method overriding.

How OOP Concepts in Java Work

OOP, concepts in Java work by letting programmers create components that can be re-used in
different ways, but still maintain security.

7.What is Object-oriented programming ..

Object-oriented programming (OOP) is a programming paradigm based on the concept of

"objects", which can contain data, in the form of fields  known as attributes or properties,
and code, in the form of procedures (often known as methods). A feature of objects is an
object's procedures that can access and often modify the data fields of the object.
In OOP, computer programs are designed by making them out of objects that interact with
one another, the most popular ones are class-based, meaning that objects
are instances of classes, which also determine their types.

8.Why pointer are not use in java

Because pointers are unsafe. 
Java uses reference types to hide pointers and programmers feel easier to deal with reference
types without pointers. ... 
Java Language does not use pointer for the reason that it works on Internet
. Applets are used on the internet