►
From YouTube: 2022 04 25 Screenshot Updates
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
to
the
chico
africa
screenshot
updates
project
meeting,
it's
25
april
topics
that
I
had
on
the
list
while
we're
waiting
for
our
participants
to
arrive
dt,
and
I
were
going
to
discuss
automation,
ideas
for
for
screenshot
updates.
A
A
And
and
that
you'd
expect
that
that's
that's
how
we
do
screenshots,
however,
what
it
that
those
words
are
not
precise
enough.
A
A
Because
in
many
of
the
examples
in
the
screenshot
sheet,
we
can
see-
let's,
let's
jump
to
one
and
take
a
look
at
it
so
here
it
says
that
the
help
icons
have
changed.
So
when
I
open
that
page
we're
going
to
see
okay,
this
one
is
the
whole
screen,
so
that
one
mechanically,
I
could
see
how
we
could
grab
it.
These
individual
pictures
of
the
health
icons
are
not
the
whole
page,
so
they
are,
they
are
something
different
and
in
fact
they
might
be
better.
A
Let's,
let's
phrase
this
as
another
way,
some
screenshots
aren't
screen
shots
at
all.
Some
screenshots,
a
few
of
the
screenshots,
are
images
in
the
jenkins
source
code,
like
the
blue
ocean
status
images
right.
So
maybe
those
we
just
say:
hey,
that's
not
a
screenshot
at
all.
It
should
just
extract
the
image
from
the
jenkins
source
code
that
is
used
for
partially
sunny,
that's
used
for
cloudy,
whatever
that
image
is
should
be,
should
be
embedded
here,
and
actually
these
may
be
up
to
date.
A
A
A
A
And
we
could,
probably,
since
jenkins,
is
java
we
could
use
here
we
go
let's,
let's
take
a
look
at
an
example
right
here
we
go
this
one
is
a
lot
of
fun
because
it
shows
exactly
how
to
do
here
is
the
here
is
the
description
that
they
use
to
describe
precisely.
Oh,
thank
you
very
much
for
the
ad
describe
precisely
how
to
how
to
pro
how
to
prepare
for
and
execute
this
this
test,
so
that
it's
written
in
english,
english
language,
adding
an
item
to
order.
A
I
want
to
be
able
to
add
an
item
to
a
current
order.
Scenario
describes
what
we're
going
to
do
before
we
start
the
test.
I
have
not
yet
ordered
anything
as
a
pre-precondition,
then
I
go
to
the
burgers
category.
Select
a
cheeseburger
have
a
new
order
and
the
order
has
one
item
in
it.
So
this
is
described
and
then
it
gives
data.
That's
used
to
describe
it.
So
there's
a
category
in
the
category
sandwiches.
A
I
have
the
item:
a
chicken
sandwich,
price
nine
dollars,
and
now
we
see
as
they
take
us
through
it,
how
that
how
that
gets
implemented
and-
and
they
really
are
creating
a
a
testing
description-
language
which
I
think
could
also
be
a
screenshot
description.
Language
in
this
case
is
one
idea
of
how
this
kind
of
thing
has
been
done.
A
B
Yes,
but
definitely
so
I
was
not
aware
of
the
pie
dog
thing
I'll
look
into
it.
I
have
done
some
behavioral
driven
development
bdd
in
the
past
and
familiar
with
cucumber
what
exactly
what
you
showed
right
so
yeah.
So
that's
something
I'm
familiar
with,
and
I
never
thought
that
it
would.
It
could
be
used
for
something
like
this.
So
that's
it's
a
new
way
to
look
at
it
and
yeah.
That's
something
again
I'll,
definitely
look
into
when
you
talked
about
screenshot
automation.
B
The
first
thing
that
came
to
my
mind
was
actually
those
end-to-end
end-to-end
testing
libraries
in
the
front
end
that
we
have
so
in
front
and
like
if
you
want
to
test
your
login
page,
for
example,
it
would
just
spin
up
an
instance.
It
will
actually
type
in
the
login
it
will,
you
know
automatically
type
in
the
login
credentials,
hit
the
login
button.
It
will
actually
happen
that
right.
B
So
I
thought
if
we
have
a
part
to
actually
go
to
the
page
where
the
screenshot
is
in
the
jenkins
deployment,
we
can
actually
write
an
end-to-end
test
like
an
interactive
test
as
you're
mentioning
that
actually
does
that
and
there
there
we
can
have
that
in,
and
this
is
something
hypothetical,
I'm
not
sure.
B
How
will
you
capture
a
particular
section
of
the
screen
taking
the
screen
is
an
easy
task,
as
you
mentioned,
taking
screenshot
of
the
whole
scene,
but
yeah
we'll
have
to
see
how
we
can
do
a
section
of
the
screen
and
then
that
can
be
basically
will
be
the
updated
screenshot
and
we
can
just
update
it.
B
So
that's
one
thing
that
I
thought
of
I've
used
cypress
and
all
the
open
source
tools
that
are
there
cypress
dot
io
in
the
past,
and
I
think
we
can
give
it
a
try
as
well
how
how
easy
or
difficult
it
would
be
to
write
something.
A
Yeah
and
cypress.I
is
an
example
of
of
end
to
end
test
automation
right
with
a
web
browser.
Is
that
correct,
I'm
not
experienced
with
cypress
I'm
yeah,
I'm
I
had
used
selenium
once
in
the
past,
and
cyprus
is
conceptually
something
similar
right,
where
it's
it's
actually
driving
a
web
browser
and
while
driving
the
web
browser.
A
A
A
A
A
No,
oh
yes,
here
it
is
okay,
sukule
is
a
is
the
same
kind
of
thing
only
it
it
uses
very
much.
If
I
understand
correctly,
it
absolutely
uses
pictures
and
it
compares
images.
So
it's
asserting
the
context,
contents
of
images,
so
it's
quite
different
from
cyprus,
where
they're,
I
think,
they're
inserting
asserting
things
inside
the
browser.
B
A
And
then
yeah,
certainly
selenium
and
oh
there
was
a
behavior
driven
thing
around
that:
oh,
oh
ruby.
What
is
it
called
the
ruby
version?
There's
a
ruby
thing
that
does
brian
merrick.
Did
it
just
a
minute
been
a
long
time,
brian
merrick,
a
ruby
web
test?
Automation?
I
don't
remember
the
name
of
it.
A
B
It's
sahih
yeah,
but
I
haven't
used
it
just
something
that
came
up
in
a
website.
Sometime
back.
A
Okay,
all
right
so
so
it's
a
sahi
is
another
is
test
automation
for
for
desktop
apps,
yeah.
Okay,
all
right.
B
Okay,
okay
yeah,
I
think,
probably
not
something
that
we'll
end
up
using.
A
A
A
Because
it
might
be
that
we
could
conceivably
yeah
okay,
so
it
does
it
using
selenium
right.
Let's
see
where
is
it
end-to-end
test
suite
for
jenkins
automation,
server
and
plugins
tests
controlling
jenkins
under
test
through
the
ui
and
rest
apis,
so
it
has
the
benefit
that
it
knows
about
jenkins
rest
apis
and
some
of
those
rest
apis
could
be
much
more
helpful
to
do
initial
configuration
than
trying
to
drive
through
a
web
browser.
A
A
So
this
might
be
another
another
approach
where
we
say
hey,
we
want
to
get
two
gains
from.
This
is
we'll
get
a
few
more
tests
for
the
acceptance
test
harness,
and
these
things
happen
also
as
a
side
effect
to
generate
screenshots
that
we
can
use.
And
now
I
don't
see
any
mention
here
of
oh
debugging
tests
in
a
container
does
it
and
it
I
think
it
may?