[HOW TO] Use Jenkins reports

Aug 16, 2023

[HOW TO] Use Jenkins reports

#AgilitestTutorial

Thanks for checking out this tutorial on Jenkins report. We’re excited to help you get started! In this tutorial, we will see:
• How to connect Jenkins to Agilitest
• How to create a Job through Jenkins
• How to execute your jobs

Plan:
00:00 Introduction
00:26 Connect Jenkins to Agilitest
01:44 Create a Job
03:41 Execute a Job
04:51 Parameter your jobs execution
05:58 Outro

- Additional resources -
https://fr.agilitest.com/blog/test-we…

We’d love to hear your thoughts, so feel free to comment and like the video. Let us know if there are any topics you’d like us to cover in future videos!
——————————————
Subscribe to our channel to get video updates. 🔔
LinkedIn: https://www.linkedin.com/company/agil…
Twitter: https://twitter.com/agilitest
Instagram: https://www.instagram.com/agilitest/
Facebook: https://www.facebook.com/agilitest
GitHub: https://github.com/pierrehub2b/action…
——————————————
🦅 About Agilitest
Agilitest offers a unique approach to the design of automated functional tests. It makes it easy for testers – both technical and functional – to create, maintain and execute robust automated functional tests.

Request a demo: https://www.agilitest.com/book-demo

Learn more about Agilitest at https://www.agilitest.com/
——————————————
#TestAutomation #AgileTesting #SoftwareTesting #Testing #TestAutomationTools #TestAutomationCourses

Content

0.25 -> [Music]

9.36 -> hello my name is mod i'm an automated

11.519 -> test conceptor and welcome to this

13.28 -> tutorial about jenkins executions in

15.599 -> agility test in this tutorial we will

17.6 -> see how to connect jenkins to agility

20 -> test then we'll see how to create a job

22.56 -> through jenkins and finally we'll see

24.8 -> how to execute your job

27.68 -> jenkins is a complete tool with many

29.84 -> parameters agility test offers a radius

32.559 -> menu with basic options when you want to

35.36 -> automate the execution of your tests you

38 -> can use jenkins from agility tests

40.559 -> to do this click on the manage execution

43.2 -> suits button and then click on the

44.8 -> jenkins integration button to have

47.12 -> access to the jenkins address in agility

49.84 -> test

50.96 -> right now jenkins is not connected to

53.76 -> connect jenkins on a julie test you do

56 -> it by directly clicking here on the

58.32 -> jenkins icon or you can connect it from

61.12 -> the tools right here on the jenkins

63.44 -> server part

65.199 -> for a first installation the tool part

67.439 -> will be shown like this you just have to

69.92 -> click on embed server then you have to

73.28 -> enter a port available

75.36 -> so for this example we'll go with 9000

80.32 -> and then you just have to click on the

82.4 -> download button

84.24 -> now if we go back to jenkins already

86.56 -> installed in a gd test click on the

88.799 -> connect button to connect jenkins to

91.04 -> agility test

92.24 -> this will open a web page that shows a

94.4 -> different project you have opened on a

96.24 -> daily test with test status represented

99.2 -> by weather conditions

104.079 -> in the second part we're going to see

105.68 -> how to create a job on jenkins from

107.92 -> agility tests and how to manage its

110.079 -> parameters

111.68 -> now with jenkins open we want to launch

114.479 -> a job for that we are going to create a

117.119 -> new job by clicking on this button next

119.759 -> to the jenkins icon

121.92 -> here for this example we can leave the

123.92 -> name new job jenkins we can also add a

127.2 -> description and then we add all the

129.039 -> parameters we want

130.959 -> by clicking on generate report it will

133.36 -> generate the same report than agility

135.52 -> tests we can also use the git repository

139.28 -> when the project is already managed by

141.2 -> git

142 -> and you can also click on maven job that

144.56 -> will make maven take action in the

146.959 -> execution

148.8 -> then you can manage the launching

150.64 -> parameters so here we want our job to

153.599 -> have an automatic launch for that click

156.239 -> on whichever day you want

158 -> here we'll only select monday

160.64 -> you have also other options like your

163.2 -> job being launched every weeks or only

166 -> the first day of the month etc etc

169.519 -> then you can define the work hours with

172.239 -> a 24 hour format

174.56 -> for example here we want our job to be

177.12 -> launched between eight and nine o'clock

179.36 -> in the morning it will automatically

181.36 -> execute the test between eight and or

183.12 -> nine o'clock there are no fixed hours

186.319 -> then if you click on the continuous

187.84 -> button the test will be executed

190.319 -> multiple times

192.239 -> on the sweet list part you can add the

194.319 -> suite you want to work with for that

197.04 -> click on the add button

198.48 -> select the suite you want to execute and

200.4 -> drag and drop it into the suites list

203.36 -> if you have an email server you can

205.36 -> choose to have notifications sent to it

207.92 -> in order to have a better understanding

210.319 -> of the job you are executing

213.04 -> once this is all done you can save all

215.68 -> your parameters

217.04 -> as you can see the display is the same

219.28 -> as the project builder

221.84 -> in this final part we are going to see

223.84 -> how to execute the job we've just

226.48 -> created

228.08 -> here we have a script which is very

230.319 -> simple it will only launch google from

232.799 -> chrome click on the pop-up to accept the

235.36 -> gdrp and then close the channel

238.64 -> we added discrete to the suite we've

241.68 -> created called test xe which is within

245.04 -> the job new job jenkins

248 -> we can find our parameters by clicking

250.48 -> on the pen button on our job line which

253.36 -> is only available if the job is not

255.439 -> executed

256.799 -> then if you want to execute your job you

259.199 -> have to select it by checking the box

261.359 -> and then click on the execute button

264.56 -> if you go back on your web page you can

266.639 -> see that the job is in the waiting line

269.199 -> and then it will be launched

271.199 -> if you click on it you can have access

272.96 -> to the build while the test is executed

275.52 -> at the same time

277.04 -> finally jenkins will tell you if the

279.44 -> test is validated or not you have the

282.16 -> console output that will give you the

284.16 -> code from the test execution

286.32 -> you can click on the ats execution suite

288.96 -> to see the agility test report

292.16 -> if you want you can launch your build

294.16 -> again by clicking here or directly from

297.199 -> agility test like we did earlier

299.6 -> we now have a little symbol which

301.52 -> express the weather statue of the job

305.44 -> if you want to configure jenkins

307.84 -> differently

309.12 -> click on the job and then click on

310.88 -> configure you will have access to all

313.28 -> the parameters including those you have

315.759 -> seen on agilities as we can see here

318.479 -> with the work hours parameters

320.8 -> represented on a

322.84 -> jenkins finally you have these buttons

326.8 -> this one is to synchronize your

329.12 -> information from jenkins

331.52 -> this one is to go to the tools window

333.919 -> directly here you can stop jenkins for

336.56 -> example and leave it connected or you

338.96 -> can also disconnect it jenkins will all

341.759 -> be always be disconnected every time you

344.16 -> open agility test on your computer

346.96 -> then you have this button which is to

348.96 -> open the project page and finally this

352.4 -> button will open the jenkins

354.4 -> configuration which is useful for the

356.639 -> remote server

358.72 -> so that's it for this tutorial thank you

360.88 -> for listening and i will see you next

362.639 -> time bye

Source: https://www.youtube.com/watch?v=jV3abZrfbeA