2019 - All About Testing 2019

What is the recipe for successful achievement?

To my mind there are just four essential ingredients: Choose a career you love, give it the best there is in you, seize your opportunities, and be a member of the team.

“All our dreams can come true, if we have the courage to pursue them.”

“I’m a great believer in luck, and I find the harder I work, the more I have of it.”

Success unshared is failure.

To make our way, we must have firm resolve, persistence, tenacity. We must gear ourselves to work hard all the way. We can never let up.

"Everyone you will ever meet knows something you don't."

he fact that I can plant a seed and it becomes a flower, share a bit of knowledge and it becomes another's, smile at someone and receive a smile in return, are to me continual spiritual exercises.

The secret of success is to do the common things uncommonly well.

Good things come to people who wait, but better things come to those who go out and get them.

Tuesday 15 October 2019

Cross Bridges hiring for QA for their Product based client

Send resume to: venkatesh@crossbridges.co.in

Experience required for the Job: 2 - 5 years
Annual Salary of the Job: 2.00 - 12.00 Lacs
Job Location: Bengaluru/Bangalore
Cross Bridges - A premiere Talent search firm with Pan India reach.
With a deep understanding of the mission-critical needs of corporations, Cross Bridges recognizes the need for agility and influence in the ecosystem to produce results. Our customers often compliment us on our research capabilities and turn- around timelines.

We have an interesting opening for Manual Testing, QA, Linux, Java, Soap professionals with one of our US Based product development clients in Bangalore.

If you are interested in the role, please share your updated CV along with your contact details, so that we can call you back and brief you more on the requirement.


Recruiter
Venkatesh
PH:9513555477

Cognizant drive on Oct 19(Bangalore) for Performance Testing

Send resume to: Agisha.K.S@cognizant.com

Immediate job opening for Performance Testing with Cognizant! Bangalore Joining!!

Interview location: Bangalore

Job Location: Bangalore

Available to attend F2F Interview on 19th Oct 19_Saturday: Yes /No   

 Name:

 Contact No:

 Mail ID:

Total years of Experience:

Relevant exp in Performance Testing (Load runner/Jmeter):

Current Company:

Current CTC:

Expected CTC:

Notice Period:

Current Location:

Education: 

Ex-Cognizant Employee: YES/NO

Available to attend F2F Interview on 19th Oct 19_Saturday: Yes /No   

 

Monday 14 October 2019

TestNG interview questions

1) What is default priority if it is not set in?

2) What would be happened if there is -ve priority? 

3) Why -ve priority not gets ignored and will be at higher priority? [Lower the number you set, it will be at higher priority and it is by designed]

4) If the test case has the same priority then how would it be executed? [If there are two methods with the same name in a different class then it will take class-wise in alphabetical orders and run sequentially.]

5) What is the difference between Beforeclass and Afterclass?

6) How can we write our own annotation in TestNG? 

7) Have anyone created own customized listener? 

8) How to run 1000 test cases at a time?

9) Can we run testNG.xml via command prompt? 

10) How do you handle exception in testNG?

11) There is N number of TC and few of them TC are failing, then is there any way to handle it apart from iretry listener? 

12) Can we execute selenium code using a batch file which is managed using the cucumber framework?

13) What is the difference between after group and before a group?

14) How to run test cases in parallel using testNG.xml and what will happen when there is parallel execution using the same data provider?

15) How do you manage, if there are multiple threads are running using TestNG and writing data in an excel sheet? 

16) How to run the same test case multiple times?

17) How to do Cross Browser Testing using Selenium WebDriver?

18) How do you execute multiple test cases in a single web driver instance?

Friday 4 October 2019

Payment Gateway Testing Checklist and Test Cases

The following checklist can be helpful for testers and could be used as a reference:

1) Set up a payment processor sandbox.

2) Gather test credit card numbers that would be used for testing different credit cards. As an example, such information for the Braintree payment processor can be found at Braintree payments.

3) Verify the behavior of the application when a transaction is successful.

4) After a successful transaction verify if the payment gateway returns to your application to show some kind of successful transaction/confirmation message.

5) Verify that the customer gets some kind of transaction confirmation notification like Order confirmation email, etc. if the transaction is successful.

6) Check what happens if a payment fails or payment processor stops responding- is there any error message?

7) Verify the application behavior with browser popup blocker on and off. This may be helpful if any confirmation messages are being displayed in the popup.

8) Verify different fraud prevention/security settings.
For example, if customer billing information does not match with the address provided to the issuing bank- any mismatch will result in transaction decline.

9) Verify the transaction entries in the database if the tester has access to the Application database.

10) Check what happens when a customer session expires.

11) Check the console during the entire transaction and report any console errors that are observed.

12) Verify that that transaction is done on a secure channel.
For example, the checkout pages may be HTTPS versus the rest of the website that is HTTP pages.

13) Verify that the payment processor currency is set up correctly.
For example, if the application/website is a Canadian company/retailer, the payment processor should be set up to accept CAD currency.

14) If the applications have multiple payment options like Credit card and PayPal together, both payment options need to individually tested from end to end.

15) Verify that refund or void amount (from payment processor admin portal) is the same as the transaction amount. In no case, the refund/void amount should exceed the transaction amount.

Database Testing Test Cases

1. Check if correct data is getting saved in the database upon successful page submit

2. Check values for columns which are not accepting null values

3. Check for data integrity. Data should be stored in single or multiple tables based on design

4. Index names should be given as per the standards e.g. IND_<Tablename>_<ColumnName>

5. Tables should have a primary key column

6. Table columns should have description information available (except for audit columns like created date, created by, etc.)

7. For every database add/update operation log should be added

8. Required table indexes should be created

9. Check if data is committed to the database only when the operation is successfully completed

10. Data should be rolled back in case of failed transactions

11. Database name should be given as per the application type i.e. test, UAT, sandbox, live (though this is not a standard it is helpful for database maintenance)

12. Database logical names should be given according to database name (again this is not standard but helpful for DB maintenance)

13. Stored procedures should not be named with prefix “sp_”

14. Check values for table audit columns (like createddate, createdby, updatedate, updatedby, isdeleted, deleteddate, deletedby etc.) are populated properly

15. Check if input data is not truncated while saving. The field length is shown to the user on-page and in database schema should be same

16. Check numeric fields with minimum, maximum, and float values

17. Check numeric fields with negative values (for both acceptance and non-acceptance)

18. Check if radio button and dropdown list options are saved correctly in the database

19. Check if database fields are designed with correct data type and data length

20. Check if all table constraints like Primary key, Foreign key, etc. are implemented correctly

21. Test stored procedures and triggers with sample input data

22. Input field leading and trailing spaces should be truncated before committing data to the database

23. Null values should not be allowed for Primary key column

Friday 27 September 2019

Manual Test Cases for Pen


Installation Testing:

1. Check if all parts of the pen are fitting properly and no loose-fitting. 
2. Check if the pen ball is fitted properly and the ball is moving with ease. 

UI Testing :

3. Check if the dimension of the pen as per mentioned in the requirement. 
4. Size and shape should be confirmable for writing.
5. Logo on the pen should be properly printed.

Usability Testing:

6. Check if the grip on the pen is superior. 
7. Check if the pen is writing smoothly with continuous and not breaking while writing.
8. Check if pen ink is not getting blemish while writing on the paper.
9. Check if the pressure needs to be applied on the pen to write down on the page with least efforts.
10. Check if the pen is usable for similar refills of different brands.

Functional Testing:

11. Check if the pen is writing on the page properly. [
12. Check if the ink on the paper belongs with the similar color as what we see in the refill.
13. Check if written on paper is not getting fade out after some time. If the requirement saying about ink is waterproof then apply water on written text and check the behavior of the ink.
14. Check if the pen is making the width of the line as per the specified millimeter range. If the pen is coming with two different sets of millimeter ranges i.e. 0.5 mm and 0.7 mm then make sure that line width is properly producing by pen as per design. [Validation Testing]

15. Check if the pen is properly working in the flight where different pressure conditions. [Performance testing]

16. Check if the pen is not used for a substantial period of time and check if the ink is not clot inside the pen. Check if the user is able to access the pen with ease. [Recovery testing]

17. Check if the material used to manufacture is safe to use for chewing or kept in mouth. Generally, users are used to putting the pen in the mouth while writing, so make sure that pen is safe to put in mouth or chewing.

18. Check if the ink is not being a leak from refill in normal conditions.

19. Check if the pen is working with different writing angles like the notice is displayed on notice board and user want to write on the notice board.

20. Check if the flow of ink is consistent while writing. The Badly designed pens have a problem with uneven ink flows.

21. Check if the pen ink is not getting dry very quickly or very slowing. While writing on page ink coming out of the pen point, so it should neither dry quickly nor dry too late.

Capability testing

22. Check if the pen is properly working on Space environment if it mentioned in the requirement specifications. 

23. Check if how much longer you can able to write with the single refill of the pen.

24. Check if the pen is properly writing on different type’s surfaces like smooth paper, rough paper, wooden material, plastic, leather, steel, glass, etc.

Robustness Testing

25. Check if the pen is properly gripped on the shirt pocket and user able to carry on the pocket with ease.

26. Check if pen writing point is strong enough to bear a load of different users like some user used to write with some extra pressure on the pen tip.

Negative Test Cases for Pen:

27. Check pen stress testing by dropping pen down from the practical height and check if nothing is breaking, no any damage to pen and pen is working without any issues.

28. Hold the pen upwards direction for some time and try to write on paper.

29. Keep the pen in water and try to write on paper.

30. Check how the pen is working at different climate environmental conditions like at room temperature, different climate conditions.

Thursday 26 September 2019

Manual Test Cases For ATM Machine

Installation Testing

1. Check if all parts of a machine is fitting properly and no loose fitting properly
2. Check if the keypad is fitted properly on ATM machine
3. Verify the type of ATM machine whether it is card intake machine or card swap machine
4. Check if slots are available for all types of notes (100,500,2000 etc)

UI Testing

1. Check if machine design is as per requirement
2. Check if length, the width of the machine is as per specifications
3. Check if the logo is properly printed on ATM Machine
4. Verify if bank name and logo is placed properly
5. Check if the machine has buttons like Enter, Cancel, Clear, and 0-9 to fill the code
6. Check if ATM have a touch screen or not

Usability Testing

1. Check if the machine is working with minimum noise and if it is smooth or not
2. Check if card insertion slot is as per specifications
3. Check if there is an image or presentation to show how the card can insert from the proper side
4. Check if font available on ATM screen is as per the specifications
5. Verify that ATM screen is smooth and operational
6. Verify that there is an option available for a user to select languages
7. Verify that option available to select account type

Functional Testing

1. Check if all buttons are working properly
2. Check if the machine is asking for a PIN number before displaying card/bank details
3. Check if after filling the correct pin, it display bank account details
4. Check if a user is allowed to check available account balance
5. Check if a user is allowed to enter amount in multiple denominations on the screen like 100,500
6. Check if the user cannot fetch more amount than the total amount available into his account
7. Check if a user is allowed to enter amount again in case it was entered incorrectly
8. Check if a user is not allowed to fetch the amount more than per day transaction limit amount
9. Check if there is an option to print the transaction
10. Check if there is the session is timeout maintained for the user
11. Check if in case sudden power failure in between transaction, the transaction must be marked as null and the amount is not withdrawn from  user's account
12. Check if ATM pin change funtion is working properly or not
13. Check out the total amount in the account after debit or credit

Non Functional Testing

1. Check if the last four digits of account no is visible on printed statement or not
2. Check if a pin must be entered within 15 seconds
3. Check if ATM can be restarted or not when required
4. Verify that the ATM machine is secured enough
5. Check out that the cashbox in ATM can be opened to fill the cash
6. Check out that the inbox of printer can be opened to fill the ink or tonner
7. Check out that the paper of printer can be filled on the printer

Performance and Security Testing

1. Verify that there are a limited number of attempts for the user to enter the pin code
2. Verify that if the total number of incorrect pin attempts then user card must be block
3. Verify that if there is no money in machine then there should be the proper message is displayed
4. Try to enter the wrong pin and check that it is giving an error message or not
5. Verify that account balance is 5000 and user try to fetch 5100 then there must be an alert message
6. Verify that if user card is for saving account and he clicks on a different account like current account then there must be no process
7. Verify that message is receiving on the registered number after withdrawal
8. Check out that user is not allowed to proceed to fetch the money if he has expired ATM card

Negative Test Cases

1. Check how the machine is working at different climate conditions like at room temperature
2. Check if the user is allowed to do transaction after the session timeout for user
3. Check if the user is allowed to do more than one transaction per pin requesting
4. Check if the user fills the wrong pin then ATM is allowed to fetch the money or not

Friday 23 August 2019

Selenium Interview Questions

1.  What are the significant changes in upgrades in various Selenium versions?
Selenium v1 included only three suite of tools: Selenium IDE, Selenium RC, and Selenium Grid. Note that there was no WebDriver in Selenium v1. Selenium WebDriver was introduced in Selenium v2. With the onset of WebDriver, Selenium RC got deprecated and is not in use since. Older versions of RC is available in the market though, but support for RC is not available. Currently, Selenium v3 is in use, and it comprises of IDE, WebDriver and Grid.
IDE is used for recording and playback of tests, WebDriver is used for testing dynamic web applications via a programming interface and Grid is used for deploying tests in remote host machines.

2.  Explain the different exceptions in Selenium WebDriver.
Exceptions in Selenium are similar to exceptions in other programming languages. The most common exceptions in Selenium are:
TimeoutException: This exception is thrown when a command performing an operation does not complete in the stipulated time
NoSuchElementException: This exception is thrown when an element with given attributes is not found on the web page
ElementNotVisibleException: This exception is thrown when the element is present in DOM (Document Object Model), but not visible on the web page
StaleElementException: This exception is thrown when the element is either deleted or no longer attached to the DOM

3. What is exception test in Selenium?
An exception test is an exception that you expect will be thrown inside a test class. If you have written a test case in such way that it should throw an exception, then you can use the @Test annotation and specify which exception you will be expecting by mentioning it in the parameters. Take a look at the example below: @Test(expectedException = NoSuchElementException.class)
Do note the syntax, where the exception is suffixed with .class

4. Why and how will you use an Excel Sheet in your project?
The reason we use Excel sheets is because it can be used as a data source for tests. An excel sheet can also be used to store the data set while performing DataDriven Testing. These are the two main reasons for using Excel sheets.
When you use the excel sheet as a data source, you can store the following:
Application URL for all environments: You can specify the URL of the environment in which you want to do the testing like: development environment or testing environment or QA environment or staging environment or production/ pre-production environment.
User name and password credentials of different environments: You can store the access credentials of the different applications/ environments in the excel sheet. You can store them in an encoded format and whenever you want to use them, you can decode them instead of leaving it plain and unprotected.
Test cases to be executed: You can list down the entire set of test cases in a column and in the next column, you can specify either Yes or No which indicates if you want that particular test case to be executed or ignored.
When you use the excel sheet for DataDriven Test, you can store the data for different iterations to be performed in the tests. For example, while testing a web page, the different sets of input data that needs to be passed to the test box can be stored in the excel sheet

5. What is the use of JavaScriptExecutor?
JavaScriptExecutor is an interface which provides a mechanism to execute Javascript through the Selenium WebDriver. It provides “executescript” and “executeAsyncScript” methods, to run JavaScript in the context of the currently selected frame or window. An example of that is:
1 JavascriptExecutor js = (JavascriptExecutor) driver;
2 js.executeScript(Script,Arguments);

6. How to scroll down a page using JavaScript in Selenium?
We can scroll down a page by using window.scrollBy() function. Example:
1 ((JavascriptExecutor) driver).executeScript("window.scrollBy(0,500)");

7. How to scroll down to a particular element?
To scroll down to a particular element on a web page, we can use the function scrollIntoView(). Example:
1 ((JavascriptExecutor) driver).executeScript("arguments[0].scrollIntoView();", element);

8. How to handle keyboard and mouse actions using Selenium?
We can handle special keyboard and mouse events by using Advanced User Interactions API. The Advanced User Interactions API contains the Actions and the Action Classes that are needed for executing these events. Most commonly used keyboard and mouse events provided by the Actions class are in the table below:
Selenium functions and their explanation
Method               Description
clickAndHold()   Clicks (without releasing) the current mouse location.
dragAndDrop() Performs click-and-hold at the location of the source element, moves.
source, target() Moves to the location of the target element, then releases the mouse

9. How to send ALT/SHIFT/CONTROL key in Selenium WebDriver?
When we generally use ALT/SHIFT/CONTROL keys, we hold onto those keys and click other buttons to achieve the special functionality. So it is not enough just to specify keys.ALT or keys.SHIFT or keys.CONTROL functions.
For the purpose of holding onto these keys while subsequent keys are pressed, we need to define two more methods: keyDown(modifier_key) and keyUp(modifier_key)

Parameters: Modifier_key (keys.ALT or Keys.SHIFT or Keys.CONTROL)
Purpose: Performs a modifier key press and does not release the modifier key. Subsequent interactions may assume it’s kept pressed.
Parameters: Modifier_key (keys.ALT or Keys.SHIFT or Keys.CONTROL)
Purpose: Performs a key release.
Hence with a combination of these two methods, we can capture the special function of a particular key.
public static void main(String[] args)
{
String baseUrl = “https://www.facebook.com”;
WebDriver driver = new FirefoxDriver();
driver.get("baseUrl");
WebElement txtUserName = driver.findElement(By.id(“Email”);
Actions builder = new Actions(driver);
Action seriesOfActions = builder
.moveToElement(txtUerName)
.click()
.keyDown(txtUserName, Keys.SHIFT)
.sendKeys(txtUserName, “hello”)
.keyUp(txtUserName, Keys.SHIFT)
.doubleClick(txtUserName);
.contextClick();
.build();
seriesOfActions.perform();
}

10. How to take screenshots in Selenium WebDriver?
You can take a screenshot by using the TakeScreenshot function. By using getScreenshotAs() method you can save that screenshot. Example:
File scrFile = ((TakeScreenshot)driver).getScreenshotAs(outputType.FILE);

# How to set the size of the browser window using Selenium?
To maximize the size of browser window, you can use the following piece of code:
driver.manage().window().maximize(); – To maximize the window
To resize the current window to a particular dimension, you can use the setSize() method. Check out the below piece of code:
System.out.println(driver.manage().window().getSize());
Dimension d = new Dimension(420,600);
driver.manage().window().setSize(d);
To set the window to a particular size, use window.resizeTo() method. Check the below piece of code:
((JavascriptExecutor)driver).executeScript("window.resizeTo(1024, 768);");

11. Explain how you will login into any site if it is showing any authentication popup for username and password?
Since there will be popup for logging in, we need to use the explicit command and verify if the alert is actually present. Only if the alert is present, we need to pass the username and password credentials. The sample code for using the explicit wait command and verifying the alert is below:
WebDriverWait wait = new WebDriverWait(driver, 10);
Alert alert = wait.until(ExpectedConditions.alertIsPresent());
alert.authenticateUsing(new UserAndPassword(**username**, **password**));

12. Explain how can you find broken links in a page using Selenium WebDriver?
This is a trick question which the interviewer will present to you. He can provide a situation where in there are 20 links in a web page, and we have to verify which of those 20 links are working and how many are not working(broken).
Since you need to verify the working of every link, the workaround is that you need to send http requests to all of the links on the web page and analyze the response. Whenever you use driver.get() method to navigate to a URL, it will respond with a status of 200 – OK. 200 – OK denotes that the link is working and it has been obtained. If any other status is obtained, then it is an indication that the link is broken.
But how will you do that?
First, we have to use the anchor tags <a> to determine the different hyperlinks on the web page. For each <a> tag, we can use the attribute ‘href’ value to obtain the hyperlinks and then analyze the response received for each hyperlink when used in driver.get() method.

13. What is parameterization in TestNG? How to pass parameters using testng.xml?
Parameterization is the technique of defining values in testng.xml file and sending them as parameters to the test class. This technique is especially useful when we need to pass multiple login credentials of various test environments. Take a look at the code below, in which “myName” is annotated as a parameter.
public class ParameterizedTest1{
@Test
@Parameters("myName")
public void parameterTest(String myName) {
System.out.println("Parameterized value is : " + myName);
}
}
To pass parameters using testng.xml file, we need to use ‘parameters’ tag. Look at the below code for example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name=”CustomSuite">
  <test name=”CustomTest”>
   <parameter name="myName" value=”John"/>
    <classes>
     <class name="ParameterizedTest1" />
    </classes>
  </test>
</suite>

 14. Explain what is Group Test in TestNG?
In TestNG, methods can be categorized into groups. When a particular group is being executed, all the methods in that group will be executed.  We can execute a group by parameterizing it’s name in group attribute of @Test annotation. Example: @Test(groups={“xxx”})
@Test(groups={“Car”})
public void drive(){
system.out.println(“Driving the vehicle”);
}
@Test(groups={“Car”})
public void changeGear() {
system.out.println("Change Gears”);
}
@Test(groups={“Car”})
public void accelerate(){
system.out.println(“Accelerating”);
}

15. How does TestNG allow you to state dependencies? Explain it with an example.
Dependency is a feature in TestNG that allows a test method to depend on a single or a group of test methods. Method dependency only works if the “depend-on-method” is part of the same class or any of the inherited base classes (i.e. while extending a class). Syntax:
@Test(dependsOnMethods = { “initEnvironmentTest” })
@Test(groups={“Car”})
public void drive(){
system.out.println(“Driving the vehicle”);
}
@Test(dependsOnMethods={“drive”},groups={cars})
public void changeGear() {
system.out.println("Change Gears”);
}
@Test(dependsOnMethods={“changeGear”},groups={“Car”})
public void accelerate(){
system.out.println(“Accelerating”);
}

16. Explain what does @Test(invocationCount=?) and @Test(threadPoolSize=?) indicate.
@Test(invocationCount=?) is a parameter that indicates the number of times this method should be invoked.
@Test(threadPoolSize=?) is used for executing suites in parallel. Each suite can be run in a separate thread.
To specify how many times @Test method should be invoked from different threads, you can use the attribute threadPoolSize along with invocationCount. Example:
@Test(threadPoolSize = 3, invocationCount = 10)
public void testServer() {
}

Jenkin Interview Questions for Testers

Q1. What is Jenkins?
My suggestion is to start this answer by giving a definition of Jenkins.
Jenkins is an open-source automation tool written in Java with plugins built for Continuous Integration purpose. Jenkins is used to build and test your software projects continuously making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. It also allows you to continuously deliver your software by integrating with a large number of testing and deployment technologies.
Once you have defined Jenkins give an example, you can refer the below-mentioned use case:
First, a developer commits the code to the source code repository. Meanwhile, the Jenkins server checks the repository at regular intervals for changes.
Soon after a commit occurs, the Jenkins server detects the changes that have occurred in the source code repository. Jenkins will pull those changes and will start preparing a new build.
If the build fails, then the concerned team will be notified.
If the build is successful, then Jenkins deploys the built-in the test server.
After testing, Jenkins generates feedback and then notifies the developers about the build and test results.
It will continue to check the source code repository for changes made in the source code and the whole process keeps on repeating.
Jenkins Architecture - DevOps Interview Questions Jenkins - Edureka
The interviewer now knows what is Jenkins but why we use it, there are many other CI tools as well, so why Jenkins? the next question in this Jenkins interview questions will deal with that answer.

Q2. What are the benefits of using Jenkins?
I will suggest you include the following benefits of Jenkins if you can recall any other benefit apart from the below-mentioned points you can include that as well.
At the integration stage, build failures are cached.
For each change in the source code, an automatic build report notification is generated.
To notify developers about build report success or failure, it is integrated with LDAP mail server.
Achieves continuous integration agile development and test driven development.
With simple steps, the maven release project is automated.
Easy tracking of bugs at an early stage in a development environment than production.
Interviewer: Okay Jenkins looks like a really cool tool, but what are the requirements for using Jenkins?

Q3. What are the pre-requisites for using Jenkins?
Answer to this is pretty straightforward To use Jenkins you require:
A source code repository which is accessible, for instance, a Git repository.
A working build script, e.g., a Maven script, checked into the repository.
Remember, you have mentioned Plugins in your previous answer, so the next question in this Jenkins interview questions blog will be regarding Plugins.

Q4. Mention some of the useful plugins in Jenkins?
Below I have mentioned some important Plugins:
Course Curriculum
DevOps Certification Training
Instructor-led SessionsReal-life Case StudiesAssignmentsLifetime Access
Maven 2 project
Git
Amazon EC2
HTML publisher
Copy artifact
Join
Green Balls
Jenkins Plugins - Jenkins Interview Questions - Edureka
These Plugins I feel are the most useful plugins, if you want to include any other Plugin that is not mentioned above, you can add that as well, but make sure you first mention the above-stated plugins and then add your own.

Q5. Mention what are the commands you can use to start Jenkins manually?
For this answer I will suggest you go with the below mentioned flow:
To start Jenkins manually open the Console/Command line, then go to your Jenkins installation directory. Over there you can use the below commands:
To start Jenkins: jenkins.exe start
To stop Jenkins: jenkins.exe stop
To restart Jenkins: jenkins.exe restart

Q6. Explain how you can set up Jenkins job?
My approach to this answer will be to first mention how to create a Jenkins job.
Go to Jenkins top page, select “New Job”, then choose “Build a free-style software project”.
Now you can tell the elements of this freestyle job:
Optional SCM, such as CVS or Subversion where your source code resides.
Optional triggers to control when Jenkins will perform builds.
Some sort of build script that performs the build (ant, maven, shell script, batch file, etc.) where the real work happens.
Optional steps to collect information out of the build, such as archiving the artifacts and/or recording Javadoc and test results.
Optional steps to notify other people/systems with the build result, such as sending e-mails, IMs, updating issue tracker, etc..

Q7. Explain how to create a backup and copy files in Jenkins?
Answer to this question is really direct.
To create a backup all you need to do is to periodically back up your JENKINS_HOME directory. This contains all of your build jobs configurations, your slave node configurations, and your build history. To create a back-up of your Jenkins setup, just copy this directory. You can also copy a job directory to clone or replicate a job or rename the directory.
Learn Jenkins With DevOps Now

Q8. How will you secure Jenkins?
The way I secure Jenkins is mentioned below if you have any other way to do it than mention that:
Ensure global security is on.
Ensure that Jenkins is integrated with my company’s user directory with the appropriate plugin.
Ensure that the matrix/Project matrix is enabled to fine-tune access.
Automate the process of setting rights/privileges in Jenkins with custom version controlled script.
Limit physical access to Jenkins data/folders.
Periodically run security audits on same.
I hope you have enjoyed the above set of Jenkins interview questions, the next set of questions will be more challenging, so be prepared.
Course Curriculum
DevOps Certification Training

Q9 Explain how you can deploy a custom build of a core plugin?
Below are the steps to deploy a custom build of a core plugin:
Stop Jenkins.
Copy the custom HPI to $Jenkins_Home/plugins.
Delete the previously expanded plugin directory.
Make an empty file called <plugin>.hpi.pinned.
Start Jenkins.

Q10. What is the relation between Hudson and Jenkins?
You can just say Hudson was the earlier name and version of current Jenkins. After some issue, the project name was changed from Hudson to Jenkins.

Q11. What you do when you see a broken build for your project in Jenkins?
There can be multiple answers to this question I will approach this task in the following way:
I will open the console output for the broken build and try to see if any file changes were missed. If I am unable to find the issue that way, then I will clean and update my local workspace to replicate the problem on my local and try to solve it.
If you do it in a different way then just mention that in your answer.

Q12. Explain how you can move or copy Jenkins from one server to another?
I will approach this task by copying the jobs directory from the old server to the new one. There are multiple ways to do that, I have mentioned it below:
You can:
Move a job from one installation of Jenkins to another by simply copying the corresponding job directory.
Make a copy of an existing job by making a clone of a job directory by a different name.
Rename an existing job by renaming a directory. Note that if you change a job name you will need to change any other job that tries to call the renamed job.

Q13. What are the various ways in which build can be scheduled in Jenkins?
You can schedule a build in Jenkins in the following ways:
By source code management commits
After completion of other builds
Can be scheduled to run at a specified time ( crons )
Manual Build Requests

Q14. What is the difference between Maven, Ant, and Jenkins?
Maven and Ant are Build Technologies whereas Jenkins is a continuous integration tool.

Q15. Which SCM tools Jenkins supports?
Below are Source code management tools supported by Jenkins:
AccuRev
CVS,
Subversion,
Git,
Mercurial,
Perforce,
Clearcase
RTC
Now, the next set of Jenkins interview questions will test your experience with Jenkins.

Q16. What are the two components Jenkins is mainly integrated with?
According to me, Jenkins is mainly integrated with the following:
Version Control system like GIT, SVN.
Build tools like Apache Maven.