xLM Continuous Validation Demos

xLM for CV Presentation

Welcome to xLM's presentation. This presentation is designed specifically to showcase our continuous validation capabilities.

Managed Services

This short presentation gives you an overview of how xLM's Managed Services work. It also includes our Tech Stack.

xLM Platform : Feature File

This video showcases how our Feature Files work. This is the foundation of our Continuous Validation framework.

xLM Platform : Pipeline Demo

This is a short 3 minute video that showcases xLM's Continuous Validation Platform in action. In this demo you can watch how our pipeline runs and executes automated test cases.

xLM Platform : GxP Reports

This is a short video that show cases a typical output from a validation run. Whenever a Continuous Validation pipeline is run, the output is a secure PDF that is a total package with all the environment details, test results, screenshots, log files, etc.. The final output is a nice package that is autogenerated with bookmarks, cover page and signature pages.

xLM Platform : Client Portal

This is a short video to walk you through our client portal. Every single subscription gets a dedicated portal where all the artifacts are organized and presented to the client.

1
00:00:00,450 --> 00:00:02,354
Welcome to xLM's presentation.

2
00:00:02,554 --> 00:00:06,921
This presentation is designed specifically to showcase our continuous validation capabilities.

3
00:00:09,071 --> 00:00:12,972
The agenda for today is to introduce xLM
Continuous Validation.

4
00:00:12,972 --> 00:00:17,089
This will be followed by describing what
is Continuous Validation.

5
00:00:17,089 --> 00:00:19,112
Lastly I will let you know Why xLM?

6
00:00:21,462 --> 00:00:23,736
We were established in 1996.

7
00:00:23,936 --> 00:00:28,371
Since then we are focused on Technology and Compliance in the GxP Space.

8
00:00:28,371 --> 00:00:32,287
We have executed projects in all the
continents except Africa.

9
00:00:32,287 --> 00:00:36,353
We provide GxP Continuous Validation to
Life Science companies.

10
00:00:36,353 --> 00:00:42,340
We also provide AI/ML managed solutions in Industrial IoT as well as GxP Data Integrity domains.

11
00:00:42,340 --> 00:00:45,519
All our managed services have embedded continuous

12
00:00:45,519 --> 00:00:49,510
validation so that every service is GxP
compliant out of the box.

13
00:00:51,660 --> 00:00:56,231
I am very glad to let you know that xLM was chosen by Ted Danson's Advancements TV.

14
00:00:56,231 --> 00:00:59,097
We were featured in their National TV Show in 2023.

15
00:00:59,097 --> 00:01:03,190
In this show we were the only Tech Company from the Life Sciences domain.

16
00:01:05,540 --> 00:01:07,965
What can Continuous Validation do?

17
00:01:08,665 --> 00:01:10,846
Our goal at xLM is to provide "lights out"

18
00:01:10,846 --> 00:01:13,990
validation automation for any Cloud or
On-prem software.

19
00:01:14,490 --> 00:01:19,944
Our service is designed to maintain any customer instance in a "validated state" on an ongoing basis.

20
00:01:20,444 --> 00:01:25,705
We manage our client's instances in a "validated state" through patches, releases and upgrades.

21
00:01:26,205 --> 00:01:28,836
Continuous Validation means total automation.

22
00:01:29,336 --> 00:01:32,672
Human intervention is only needed when
there is an exception.

23
00:01:32,672 --> 00:01:35,303
Even here the exception ticket is automatically

24
00:01:35,303 --> 00:01:38,447
created with all required evidences
including log files.

25
00:01:40,597 --> 00:01:42,856
Yeah, let us talk about the benefits.

26
00:01:42,856 --> 00:01:47,593
Continuous Validation is all about reducing Compliance and Business risks.

27
00:01:48,093 --> 00:01:54,069
Compressing Validation Timelines by more than 75% and reducing validation cost by more than 50%.

28
00:01:54,069 --> 00:01:58,587
All this while increasing test coverage and performing 100% regression.

29
00:01:58,587 --> 00:02:03,543
Manual validation is definitely outdated and cannot compete with our platform.

30
00:02:05,693 --> 00:02:08,401
There are more benefits to Continuous Validation.

31
00:02:08,401 --> 00:02:11,172
We add value supporting our clients with the ability

32
00:02:11,172 --> 00:02:16,588
to handle frequent changes and at the same time ensuring data integrity compliance is only increased.

33
00:02:17,288 --> 00:02:18,670
How do we do this?

34
00:02:18,870 --> 00:02:21,641
We use latest software testing methods that include

35
00:02:21,641 --> 00:02:25,986
positive, negative testing, data driven testing, combinatorial testing, etc..

36
00:02:27,236 --> 00:02:30,773
Quickly to summarize...Continuous Validation is built

37
00:02:30,773 --> 00:02:33,795
on a robust feature based automation framework,

38
00:02:33,795 --> 00:02:37,037
provides real-time KPIs, integrates into any CI/CD

39
00:02:37,037 --> 00:02:40,354
pipeline, fully complies with 21 CFR Part 11 and Annex

40

00:02:40,354 --> 00:02:43,891
11, supports test case repurposing.....with a built-in

41
00:02:43,891 --> 00:02:48,902
ability to deploy the same test case for functional testing, load testing, etc..

42
00:02:52,052 --> 00:02:56,649
Here is a quick sample of a dashboard that
provides real-time KPIs for every validation release.

43
00:03:00,299 --> 00:03:02,220
This is another example of a dashboard.

44
00:03:02,220 --> 00:03:05,131
Such a dashboard provides real-time data
on test failures.

45
00:03:08,781 --> 00:03:10,554
Here is a list of sample clients.

46
00:03:10,554 --> 00:03:13,313
You can see our client logos range from Enterprise

47
00:03:13,313 --> 00:03:17,714
Pharma companies to technology partners to non-profit/government agencies.

48
00:03:20,364 --> 00:03:24,472
This slide provides some of the platforms for which we have developed Continuous Validation.

49
00:03:27,122 --> 00:03:33,840
Ultimately we have made every single client, both big and small, smile when they hear the word "validation".

50
00:03:33,840 --> 00:03:38,491
We have consistently reduced validation spend and compressed timelines.

51
00:03:38,491 --> 00:03:44,101
This has allowed our clients to deploy their resources on their higher priority projects.

52
00:03:44,851 --> 00:03:50,774
I would like to thank you for your time and interest in xLM's Continuous Validation services.

53
00:03:50,774 --> 00:03:53,811
If you need more information, please visit us at

54
00:03:53,811 --> 00:03:59,202
continuousvalidation.com or send us an email at info@continuousvalidation.com.

55
00:03:59,402 --> 00:04:00,585
THANK YOU.

1
00:00:00,250 --> 00:00:02,061
Welcome to this short presentation.

2
00:00:02,061 --> 00:00:04,806
I will walk you through how xLM's
Managed Services work.

3
00:00:06,956 --> 00:00:10,448
I will describe how our Managed Service for Continuous Validation works.

4
00:00:10,448 --> 00:00:13,602
I will also walk you through our
Continuous Validation Framework.

5
00:00:15,752 --> 00:00:18,365
The first phase is Planning and Design.

6
00:00:18,365 --> 00:00:21,612
Here our client success team will work with you to

7
00:00:21,612 --> 00:00:25,572
prepare the Validation Plan followed by
the U R S, F R S and C S.

8
00:00:25,572 --> 00:00:31,671
They will also perform a Risk Assessment and will initiate the creation of the tracematrix.

9
00:00:33,821 --> 00:00:36,418
Then comes the fun part where our QA team will

10
00:00:36,418 --> 00:00:42,035
navigate through all the use cases for validation and generate a Feature File for each use case.

11
00:00:42,035 --> 00:00:46,177
The feature file is written in quasi English using the Gherkins model.

12
00:00:46,177 --> 00:00:48,737
Then our Test Automation team takes over.

13
00:00:48,737 --> 00:00:54,588
They write the code for each step in the feature file to drive the browser, make an A P I call, etc..

14

00:00:54,588 --> 00:00:59,225
The Test Automation team creates a DEV pipeline which will execute various steps.

15
00:00:59,225 --> 00:01:02,048
These include creating a V M on the fly, loading our

16
00:01:02,048 --> 00:01:05,138
framework and the test automation code, executing the

17
00:01:05,138 --> 00:01:09,709
test cases automatically, generating the secure PDF report with all evidences.

18
00:01:09,709 --> 00:01:13,002
This PDF report includes all the details
of the test suite.

19
00:01:13,002 --> 00:01:16,228
Such details also include screenshots, log files, etc..

20
00:01:18,378 --> 00:01:23,874
Once the DEV pipeline results are approved by QA, then it is promoted to the Release pipeline.

21
00:01:23,874 --> 00:01:28,172
This Release pipeline run is a formal validation run executed by QA only.

22
00:01:28,172 --> 00:01:33,174
Once this pipeline is run, the auto generated PDF reports are reviewed and approved.

23
00:01:33,174 --> 00:01:36,063
Then they are routed for Client approval as well.

24
00:01:36,063 --> 00:01:40,514
Finally all the approved Validation PDF reports are uploaded and organized in the Customer Portal.

25
00:01:42,664 --> 00:01:47,056
Let us talk a little bit about our Tech Stack which we call the xLM Framework.

26
00:01:47,056 --> 00:01:49,984
This framework is developed and qualified by xLM.

27
00:01:49,984 --> 00:01:54,237
It provides all the features required to run our managed service engine.

28
00:01:54,437 --> 00:01:55,914
We use a B D D model.

29
00:01:56,114 --> 00:02:00,219
B D D stands for Behavior Driven Development which is an industry standard.

30
00:02:00,219 --> 00:02:03,013
Feature Files are written in Gherkins language.

31
00:02:03,013 --> 00:02:08,056
These Feature Files are used by the Development Team to create the Test Automation Code.

32
00:02:08,056 --> 00:02:12,758
This type of coding automatically drives the browser, initiates A P I calls, etc..

33
00:02:12,758 --> 00:02:15,265
For the Pipelines, we use Azure DEV Ops.

34
00:02:15,265 --> 00:02:18,280
The reporting engine is a proprietary service
developed by xLM.

35
00:02:20,630 --> 00:02:21,660
Thank You!

36
00:02:21,860 --> 00:02:23,805
For more information please visit us at

37
00:02:23,805 --> 00:02:27,990
continuousvalidation.com or send us an email at info@continuousvalidation.com.

1
00:00:00,250 --> 00:00:06,711
In this short presentation, I will walk you through how our feature files work as part of the xLM Platform.

2
00:00:06,711 --> 00:00:11,116
Feature File is the first step in the Continuous Validation life cycle.

3
00:00:11,116 --> 00:00:16,843
Typically, one of our QA team member will understand the use case by reviewing your cloud app.

4
00:00:16,843 --> 00:00:20,073
Then the QA team member will author the feature file.

5
00:00:20,273 --> 00:00:22,682
This is how we did it in the past.

6
00:00:22,882 --> 00:00:25,525
However, soon our AI/ML feature which is in

7
00:00:25,525 --> 00:00:29,196
development will automatically create
this feature file.

8
00:00:29,396 --> 00:00:31,658
Why do we need a feature file?

9
00:00:31,858 --> 00:00:34,134
Our platform is highly modularized.

10
00:00:34,134 --> 00:00:36,850
The feature file concept provides a layer of

11
00:00:36,850 --> 00:00:41,329
abstraction between the test automation code and test case definition.

12
00:00:41,329 --> 00:00:46,835
Also, the feature file provides the ability to
parametrize our test automation modules.

13
00:00:46,835 --> 00:00:50,653
Lastly, the feature file separates QA
from Development team.

00:00:50,653 --> 00:00:55,646
In other words, QA team's contract with the
Development team is the Feature File.

15
00:00:55,646 --> 00:00:59,757
Feature file is written in quasi English using
Gherkins language.

16
00:01:00,507 --> 00:01:06,557
The first section in the feature file clear states the scenario name, objective and acceptance criteria.

17
00:01:06,757 --> 00:01:09,024
Just like in a manual test case.

18
00:01:09,224 --> 00:01:12,759
This section provides clear definition
for the feature file.

19
00:01:12,759 --> 00:01:18,061
Here the feature file attempts to test the Study User Administration function in Veeva C D M S.

20
00:01:18,061 --> 00:01:22,889
The next section defines the actual sequence of logic for a test case.

21
00:01:22,889 --> 00:01:26,551
This logic is based on the Given When Then framework.

22
00:01:26,551 --> 00:01:28,887
Now you can see how a step is defined.

23
00:01:28,887 --> 00:01:35,662
What you are seeing is a step, for example, where the user has to click on Cancel and then create a new user.

24
00:01:35,662 --> 00:01:38,621
You will also see all the parameters in green.

25
00:01:38,621 --> 00:01:41,035
For example, User Name, Email, etc..

26
00:01:41,035 --> 00:01:46,797
This provides the ability to change parameters without impacting the underlying code.

00:01:46,797 --> 00:01:49,600
Now you can see more steps where there are no

28
00:01:49,600 --> 00:01:53,805
parameters but a direct sequence that
the code needs to execute.

29
00:01:53,805 --> 00:01:58,166
These include navigation, login /
logout, uploading a file, etc..

30
00:01:58,166 --> 00:02:02,137
The feature file gets pre-approved
before coding can begin.

31
00:02:02,137 --> 00:02:07,354
Equivalent to the pre-approval of a protocol or test script in the manual world.

32
00:02:08,304 --> 00:02:09,454
Thank You!

33
00:02:09,654 --> 00:02:13,842
For further information, please visit
continuousvalidation.com.

34
00:02:13,842 --> 00:02:16,803
or email us to info@continuousvalidation.com.

1
00:00:00,250 --> 00:00:05,515
This is a short 3 minute video that showcases xLM's Continuous Validation Platform in action.

2
00:00:05,515 --> 00:00:10,113
In this demo you can watch how our pipeline runs and executes automated test cases.

3
00:00:10,113 --> 00:00:13,712
Please note that this demo has been
edited for your convenience.

4
00:00:13,712 --> 00:00:16,644
I will be more than glad to organize an in person demo.

5
00:00:16,644 --> 00:00:18,910
We request about 45 minutes of your time.

6
00:00:18,910 --> 00:00:22,909
I will provide you with the contact information at the end of this video.

7
00:00:25,059 --> 00:00:27,593
Right now you can see our DEV Ops pipeline.

8
00:00:27,793 --> 00:00:29,380
It has two stages.

9
00:00:29,580 --> 00:00:35,880
The first stage runs the test cases while the second stage captures the pipeline audit trail in a report.

10
00:00:35,880 --> 00:00:39,284
In our typical validation execution, the pipeline runs

11
00:00:39,284 --> 00:00:42,760
in the cloud and builds a new VM in
which the code executes.

12
00:00:42,760 --> 00:00:46,815
In this demo, the execution is local so that you can see it in action.

13
00:00:47,315 --> 00:00:51,194
When the pipeline is running, you will see the status of various stages.

14

00:00:51,194 --> 00:00:54,039
For each stage, you can see the logging in real-time.

15
00:00:55,439 --> 00:00:58,633
These pipelines can get complex based on the project.

16
00:00:58,633 --> 00:01:01,613
It typically has steps to download the latest code

17
00:01:01,613 --> 00:01:04,665
from the repository, create a VM on the fly, load the

18
00:01:04,665 --> 00:01:08,497
various packages and initiate the
automated testing sequence.

19
00:01:08,997 --> 00:01:15,595
The real-time logging tends to be very verbose and provides a very good audit trail for the execution.

20
00:01:15,595 --> 00:01:20,252
Our framework by default captures all the logs in a secure PDF document.

21
00:01:20,752 --> 00:01:25,137
When the test step is running, you can see the results in the log in real-time.

22
00:01:25,637 --> 00:01:29,465
Such a pipeline can also include QA approvals at certain steps.

23
00:01:29,465 --> 00:01:33,365
For example, QA approval can be embedded for initiating the run.

24
00:01:33,865 --> 00:01:36,513
The best part is that these pipelines can run

25
00:01:36,513 --> 00:01:39,734
completely unattended and can even execute multiple

26
00:01:39,734 --> 00:01:45,173
stages in parallel which is required to cut down on he execution time for larger projects.

00:01:45,673 --> 00:01:50,864
Wow....now you will see that our pipeline has launched the browser to begin testing.

28
00:01:50,864 --> 00:01:54,008
The testing bot works just like a human only faster.

29
00:01:54,008 --> 00:01:56,129
It can do all the tasks in a browser.

30
00:01:56,129 --> 00:02:00,077
You can see that the bot logs in,
selects a vault, and then a study.

31
00:02:00,077 --> 00:02:02,637
It follows the script in the Feature File.

32
00:02:04,037 --> 00:02:08,824
Again the bot can mimic a human user and any transaction can be performed by it.

33
00:02:08,824 --> 00:02:15,453
It takes control of the browser, identifies various elements on the screen and then navigate accordingly.

34
00:02:15,453 --> 00:02:21,419
It can assert any piece of information on the screen and also enter values into data entry fields.

35
00:02:22,819 --> 00:02:26,811
The bot does this by understanding the
object model of the page.

36
00:02:26,811 --> 00:02:30,427
Once it does this, it can access any
element on the screen.

37
00:02:30,427 --> 00:02:36,529
The bot uses various techniques to identify
elements......like Computer Vision, XPATH, etc..

38
00:02:37,029 --> 00:02:39,378
Next you will see that it uploads a file.

39
00:02:39,378 --> 00:02:41,940

This file has a list of users to be imported.

40
00:02:41,940 --> 00:02:46,780
By performing this action, the list of users are automatically created in Veeva.

41
00:02:48,680 --> 00:02:54,350
You can also see that the bot can log into Gmail and access the notification sent by Veeva.

42
00:02:54,350 --> 00:02:59,178
It can not only access the email but also can read the relevant information.

43
00:02:59,178 --> 00:03:04,465
For example, it can figure out how to log in and validate the user creation process.

44
00:03:06,365 --> 00:03:11,802
As the bot is performing these tasks, the pipeline continues to log all steps in the audit trail.

45
00:03:11,802 --> 00:03:17,239
Such detailed audit trail helps the quality of
evidence gathered during such a validation run.

46
00:03:19,139 --> 00:03:22,456
The status of each step in the pipeline
is displayed in real-time.

47
00:03:22,456 --> 00:03:26,255
This makes it very useful in monitoring the progress of the validation run.

48
00:03:27,655 --> 00:03:32,211
Futhermore, you will see that the status of the pipeline stages are also displayed in real-time.

49
00:03:34,361 --> 00:03:37,256
This was edited to quickly showcase its power.

50
00:03:37,256 --> 00:03:40,598
It can not only access the browser and perform various

51
00:03:40,598 --> 00:03:43,568
functions, it can also launch various apps like

52

00:03:43,568 --> 00:03:48,766
browsing files, open them in Excel for example, read the data, manipulate the data.

53
00:03:48,766 --> 00:03:51,958
The capabilities are endless and only getting more

54
00:03:51,958 --> 00:03:56,042
powerful since we are integrating AI/ML, Computer Vision, etc..

55
00:03:56,242 --> 00:03:57,566
Thank you for watching this demo.

56
00:03:57,766 --> 00:04:00,892
Please go to continuousvalidation.com for more

57
00:04:00,892 --> 00:04:05,237
information or send us an email at
info@continuousvalidation.com

1
00:00:00,250 --> 00:00:04,768
This is a short video that show cases a typical output from a validation run.

2
00:00:04,768 --> 00:00:08,067
Whenever a Continuous Validation pipeline is run, the

3
00:00:08,067 --> 00:00:11,008
output is a secure PDF that is a total package with

4
00:00:11,008 --> 00:00:15,526
all the environment details, test results,
screenshots, log files, etc..

5
00:00:15,526 --> 00:00:17,965
The final output is a nice package that is

6
00:00:17,965 --> 00:00:21,838
autogenerated with bookmarks, cover page
and signature pages.

7
00:00:23,988 --> 00:00:27,016
The cover page has all the details about the system,

8
00:00:27,016 --> 00:00:31,524
test case details including an unique document number and revision number.

9
00:00:31,524 --> 00:00:34,694
The format and style are fully customizable and can be

10
00:00:34,694 --> 00:00:37,933
set up to meet the corporate guidelines
of our clients.

11
00:00:38,433 --> 00:00:40,696
The entire PDF package is set up this way to be

12
00:00:40,696 --> 00:00:44,669
consistent with the industry standards and health authority expectations.

13
00:00:44,669 --> 00:00:49,438
Since these reports are autogenerated, they are always consistent in terms of the template.

00:00:51,338 --> 00:00:53,589
The same is true of the signature page.

15
00:00:53,589 --> 00:00:57,809
This page can be auto populated with the required names of signatories.

16
00:00:58,809 --> 00:01:01,231
The table of contents is a standard feature.

17
00:01:02,231 --> 00:01:05,298
Now you are seeing the Environment details page.

18
00:01:05,298 --> 00:01:08,663
This page captures all the details of the system under

19
00:01:08,663 --> 00:01:15,395
test, the Pull Request number of the code, time zone, target application version number including the URL.

20
00:01:15,395 --> 00:01:19,882
It also captures the browser information as well as start and end times.

21
00:01:20,882 --> 00:01:23,423
You will also see the details about the number of failures as well.

22
00:01:25,323 --> 00:01:30,816
Execution summary page clears lists all the test cases, their final status as well as the results.

23
00:01:30,816 --> 00:01:34,969
You can notice that the test case number is a unique id across our platform.

24
00:01:36,869 --> 00:01:42,195
Each test case in a suite are auto numbered as shown with the test objective and acceptance criteria.

25
00:01:42,695 --> 00:01:45,621
Next you will see a table that includes the step

26
00:01:45,621 --> 00:01:50,198
number, step description, expected result as well as the actual result.

00:01:50,198 --> 00:01:53,875
The actual result has the computer
generated time stamps.

28
00:01:53,875 --> 00:01:57,914
Now you will see how screenshots are captured in the Actual Results column.

29
00:01:57,914 --> 00:02:03,363
Our platform provides the ability to turn on or off the screenshot capture feature for any given step.

30
00:02:03,363 --> 00:02:06,953
Also, we can capture the entire desktop or only the browser window.

31
00:02:06,953 --> 00:02:11,698
This flexibility is required if you would like to see the system clock in the screenshot.

32
00:02:13,598 --> 00:02:18,866
Also, the system verifies any data element that is in the screenshot through assertions.

33
00:02:18,866 --> 00:02:23,994
When such assertions are performed, it is clearly stated in the Actual Results column.

34
00:02:23,994 --> 00:02:28,321
Now you will see how our system use variables to conduct the validation run.

35
00:02:28,321 --> 00:02:31,824
It embeds all the variable values in the
respective columns.

36
00:02:33,024 --> 00:02:35,451
This feature is very important.

37
00:02:35,651 --> 00:02:38,363
For example, if a document is created during a

38
00:02:38,363 --> 00:02:41,004
previous step and the number is required for

00:02:41,004 --> 00:02:44,359

subsequent testing, the system will handled during run

40
00:02:44,359 --> 00:02:48,856
time since this typo of info is not available prior to the actual execution.

41
00:02:49,856 --> 00:02:53,651
Now you are seeing additional examples of screenshots captured during the run.

42
00:02:53,651 --> 00:02:56,994
Such screenshots can be from any application and not just the browser.

43
00:02:58,894 --> 00:03:01,568
One thing to note is that any step failures are

44
00:03:01,568 --> 00:03:06,704
clearly noted and a deviation ticket is automatically opened for root cause analysis.

45
00:03:06,704 --> 00:03:11,866
Now you can see even the bookmarks are generated on the fly and embedded in the PDF document.

46
00:03:14,366 --> 00:03:18,038
Now you are seeing a sample page from the pipeline audit trail report.

47
00:03:18,538 --> 00:03:21,469
What you will be seeing next is our platform feature

48
00:03:21,469 --> 00:03:25,422
that embeds any attachment in the relevant step and adds a hyperlink.

49
00:03:25,422 --> 00:03:28,762
Also, the attachment is available in the
same PDF package.

50
00:03:30,162 --> 00:03:32,967
Our system supports embedding any type of digital

51
00:03:32,967 --> 00:03:36,439
evidence like PDFs, text files, JPEG
files, html files, etc..

00:03:38,339 --> 00:03:41,568
Overall you see how our platform ensure data integrity.

53
00:03:41,568 --> 00:03:44,386
The system captures everything in real-time and

54
00:03:44,386 --> 00:03:47,821
prepares a secure package without any human intervention.

55
00:03:48,771 --> 00:03:51,058
Thank you for watching this video.

56
00:03:51,258 --> 00:03:52,922
For more information visit us at

57
00:03:52,922 --> 00:03:57,296
continuousvalidation.com or send us an email at info@continuousvalidation.com.

1
00:00:00,250 --> 00:00:03,096
This is a short video to walk you
through our client portal.

2
00:00:03,096 --> 00:00:05,593
Every single subscription gets a dedicated portal

3
00:00:05,593 --> 00:00:08,846
where all the artifacts are organized
and presented to the client.

4
00:00:09,046 --> 00:00:10,417
Let us take a dive.

5
00:00:11,867 --> 00:00:14,591
Now you are looking at the home page of the portal.

6
00:00:14,591 --> 00:00:17,979
This page presents the metrics from the
most recent release.

7
00:00:17,979 --> 00:00:20,968
This includes the validation status of the instance.

8
00:00:22,368 --> 00:00:25,248
It also includes various KPIs and Metrics showcasing

9
00:00:25,248 --> 00:00:28,831
snapshots and historical data associated
with runs and failures.

10
00:00:30,231 --> 00:00:32,468
Such KPIs are updated in real-time.

11
00:00:32,468 --> 00:00:35,377
Of course they are customized for each client.

12
00:00:35,377 --> 00:00:41,098
Our clients are provided easy access to their release documents and many related xLM resources.

13
00:00:41,098 --> 00:00:44,351
Now you are looking at a typical page
that outlines test cases.

00:00:44,351 --> 00:00:48,292

It also presents the model, a sequence diagram and a test coverage diagram.

15
00:00:49,692 --> 00:00:52,749
Such information makes it very easy to
review our model.

16
00:00:52,949 --> 00:00:54,910
Now you are looking at a model.

17
00:00:55,110 --> 00:00:57,449
Such a model is used to layout the test strategy.

18
00:00:57,649 --> 00:00:59,785
The model has states and actions.

19
00:00:59,985 --> 00:01:02,441
For example, Admin Setup is a State and you will see

20
00:01:02,441 --> 00:01:05,480
all the actions that either originate or
lead into this state.

21
00:01:06,881 --> 00:01:10,261
Now you are seeing a sequence diagram that depicts the sequence of test execution.

22
00:01:11,661 --> 00:01:14,074
Now you are seeing a test coverage graph.

23
00:01:14,074 --> 00:01:17,055
This graph displays the various paths taken by the

24
00:01:17,055 --> 00:01:21,029
execution model where a "green" line means the path was traversed.

25
00:01:21,029 --> 00:01:23,442
In 100% testing, all lines must be green.

26
00:01:23,442 --> 00:01:26,989
A current validation release page includes the metrics

27
00:01:26,989 --> 00:01:31,819
for the release, package information and a table with all the deliverables.

28
00:01:31,819 --> 00:01:36,724
For each deliverable, a link to the digitally approved artifact is provided.

29
00:01:36,724 --> 00:01:39,743
You can see how well our releases are organized.

30
00:01:40,693 --> 00:01:43,014
Thank you for watching this video.

31
00:01:43,214 --> 00:01:45,098
For more information, please visit

32
00:01:45,098 --> 00:01:49,557
continuousvalidation.com or send us an email to info@continuousvalidation.com.

Ready to Transform Validation for Your IaaS, PaaS, SaaS, and On-Prem Solutions?

Get Started