[WEBSITE] QA area changes, and differences between staging and production

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[WEBSITE] QA area changes, and differences between staging and production

Kay Schenk-2
I've committed changes to the QA area complete with the "index" capability
of the new test case area. I'll be working on additional changes to the QA
area over the next few days before a general announcement to QA.

NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- allows
for +Indexes automatically so displays can be  misleading in that
environment. Our default setup for -- http://www.openoffice.org/ -- does
not.

We should probably request that infra setup both these servers the same.


--
----------------------------------------------------------------------
MzK

"Less is MORE."
Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Dave Fisher
Hi Kay,

I took a look. Looks ok. Saw a css file at the end.

 I think it would be good to filter the index so that only certain mimetypes or suffixes are shown like html, pdf, ods, etc.

Regards,
Dave

Sent from my iPhone

> On Mar 30, 2018, at 12:15 PM, Kay Schenk <[hidden email]> wrote:
>
> I've committed changes to the QA area complete with the "index" capability
> of the new test case area. I'll be working on additional changes to the QA
> area over the next few days before a general announcement to QA.
>
> NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- allows
> for +Indexes automatically so displays can be  misleading in that
> environment. Our default setup for -- http://www.openoffice.org/ -- does
> not.
>
> We should probably request that infra setup both these servers the same.
>
>
> --
> ----------------------------------------------------------------------
> MzK
>
> "Less is MORE."


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Kay Schenk-2

On 03/30/2018 12:21 PM, Dave Fisher wrote:
> Hi Kay,
>
> I took a look. Looks ok. Saw a css file at the end.
>
>   I think it would be good to filter the index so that only certain mimetypes or suffixes are shown like html, pdf, ods, etc.
>
> Regards,
> Dave

Hi Dave --
That css file is needed to make the html files display correctly when
you click on them. Right off hand, I don't know how to do what you're
suggesting  with just setting HTTPD + Indexes option. :( Maybe someone
else does?

>
> Sent from my iPhone
>
>> On Mar 30, 2018, at 12:15 PM, Kay Schenk <[hidden email]> wrote:
>>
>> I've committed changes to the QA area complete with the "index" capability
>> of the new test case area. I'll be working on additional changes to the QA
>> area over the next few days before a general announcement to QA.
>>
>> NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- allows
>> for +Indexes automatically so displays can be  misleading in that
>> environment. Our default setup for -- http://www.openoffice.org/ -- does
>> not.
>>
>> We should probably request that infra setup both these servers the same.
>>
>>
>> --
>> ----------------------------------------------------------------------
>> MzK
>>
>> "Less is MORE."
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

--
------------------------------------------
MzK

"Ring out the false, ring in the true."
  -- poem "In Memoriam", Alfred Lord Tennyson

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Keith N. McKenna
In reply to this post by Kay Schenk-2
On 3/30/2018 3:15 PM, Kay Schenk wrote:

> I've committed changes to the QA area complete with the "index" capability
> of the new test case area. I'll be working on additional changes to the QA
> area over the next few days before a general announcement to QA.
>
> NOTE: the staging web site -- http://ooo-site.staging.apache.org/ -- allows
> for +Indexes automatically so displays can be  misleading in that
> environment. Our default setup for -- http://www.openoffice.org/ -- does
> not.
>
> We should probably request that infra setup both these servers the same.
>
>
Kay;

Just tried to check out ooo-site repo in preparation for completing the
download of all the Impress test cases and ran into a problem. You have
a number of files that include an * in the filename. This is no-no on
windows and causes a corrupt working copy on Windows that can not be
used. Can you update the ooo-site repo and replace those 1/2 dozen or so
files with * in the names so that I can check out a new working copy?

Also a process question. Why did you chose to put all the tests in a
single directory rather than breaking it down by application the way
they were on the testlink site? The process engineer in me says that it
would be cleaner to do it by application so that a volunteer working on
Writer doesn't have to wade through tests that do not apply to them to
find the Writer specific ones.

Regards
Keith



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Kay Schenk-2
On Mon, Apr 2, 2018 at 3:07 PM, Keith N. McKenna <[hidden email]>
wrote:

> On 3/30/2018 3:15 PM, Kay Schenk wrote:
> > I've committed changes to the QA area complete with the "index"
> capability
> > of the new test case area. I'll be working on additional changes to the
> QA
> > area over the next few days before a general announcement to QA.
> >
> > NOTE: the staging web site -- http://ooo-site.staging.apache.org/ --
> allows
> > for +Indexes automatically so displays can be  misleading in that
> > environment. Our default setup for -- http://www.openoffice.org/ -- does
> > not.
> >
> > We should probably request that infra setup both these servers the same.
> >
> >
> Kay;
>
> Just tried to check out ooo-site repo in preparation for completing the
> download of all the Impress test cases and ran into a problem. You have
> a number of files that include an * in the filename. This is no-no on
> windows and causes a corrupt working copy on Windows that can not be
> used. Can you update the ooo-site repo and replace those 1/2 dozen or so
> files with * in the names so that I can check out a new working copy?
>

​Yes, I will do that.



>
> Also a process question. Why did you chose to put all the tests in a
> single directory rather than breaking it down by application the way
> they were on the testlink site?


​An oversight on my part, but as I got into this, I did see there was a LOT
of overlap, with the former QA folks establishing categories for some very
specific areas. We can probably restructure this new area just based on
file names and move things around. I discovered on the original TestLink
site that there were MANY fine-grained categorizations that we probably
don't need.




> The process engineer in me says that it
> would be cleaner to do it by application so that a volunteer working on
> Writer doesn't have to wade through tests that do not apply to them to
> find the Writer specific ones.
>

​I thought perhaps the file names themselves would suffice for determining
categories. In any case, please feel free to organize this area further. I
would think subareas for Wrtier, Calc, Impress, Database, Drawing would be
enough -- or not.



>
> Regards
> Keith​


>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
----------------------------------------------------------------------
MzK

"Less is MORE."
Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Kay Schenk-2
a followup, see below...

On Mon, Apr 2, 2018 at 3:41 PM, Kay Schenk <[hidden email]> wrote:

>
>
> On Mon, Apr 2, 2018 at 3:07 PM, Keith N. McKenna <
> [hidden email]> wrote:
>
>> On 3/30/2018 3:15 PM, Kay Schenk wrote:
>> > I've committed changes to the QA area complete with the "index"
>> capability
>> > of the new test case area. I'll be working on additional changes to the
>> QA
>> > area over the next few days before a general announcement to QA.
>> >
>> > NOTE: the staging web site -- http://ooo-site.staging.apache.org/ --
>> allows
>> > for +Indexes automatically so displays can be  misleading in that
>> > environment. Our default setup for -- http://www.openoffice.org/ --
>> does
>> > not.
>> >
>> > We should probably request that infra setup both these servers the same.
>> >
>> >
>> Kay;
>>
>> Just tried to check out ooo-site repo in preparation for completing the
>> download of all the Impress test cases and ran into a problem. You have
>> a number of files that include an * in the filename. This is no-no on
>> windows and causes a corrupt working copy on Windows that can not be
>> used. Can you update the ooo-site repo and replace those 1/2 dozen or so
>> files with * in the names so that I can check out a new working copy?
>>
>
> ​Yes, I will do that.
>

​OK, I did a series of svn mv on the "bad" file names. My svn commands told
me this --



​some area//​
svn mv 350_Extend_Text_*_Cell_Properties_Numbers_Thousands_separator.html
350_Extend_Text_Cell_Properties_Numbers_Thousands_separator.html

A         350_Extend_Text_Cell_Properties_Numbers_Thousands_separator.html
D         350_Extend_Text_*_Cell_Properties_Numbers_Thousands_separator.html

​which should have deleted the old file and replaced/renamed it with the
old file. However, when I did the commit, the old file names are STILL
there in staging, so perhaps I need to do more to get things in sync.
Later...




>
>
>>
>> Also a process question. Why did you chose to put all the tests in a
>> single directory rather than breaking it down by application the way
>> they were on the testlink site?
>
>
> ​An oversight on my part, but as I got into this, I did see there was a
> LOT of overlap, with the former QA folks establishing categories for some
> very specific areas. We can probably restructure this new area just based
> on file names and move things around. I discovered on the original TestLink
> site that there were MANY fine-grained categorizations that we probably
> don't need.
>
> ​
>
>
>> The process engineer in me says that it
>> would be cleaner to do it by application so that a volunteer working on
>> Writer doesn't have to wade through tests that do not apply to them to
>> find the Writer specific ones.
>>
>
> ​I thought perhaps the file names themselves would suffice for determining
> categories. In any case, please feel free to organize this area further. I
> would think subareas for Wrtier, Calc, Impress, Database, Drawing would be
> enough -- or not.
> ​
>
>
>>
>> Regards
>> Keith​
>
>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> --
> ----------------------------------------------------------------------
> MzK
>
> "Less is MORE."
>



--
----------------------------------------------------------------------
MzK

"Less is MORE."
Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Keith N. McKenna
In reply to this post by Kay Schenk-2
On 4/2/2018 6:41 PM, Kay Schenk wrote:

> On Mon, Apr 2, 2018 at 3:07 PM, Keith N. McKenna <[hidden email]>
> wrote:
>
>> On 3/30/2018 3:15 PM, Kay Schenk wrote:
>>> I've committed changes to the QA area complete with the "index"
>> capability
>>> of the new test case area. I'll be working on additional changes to the
>> QA
>>> area over the next few days before a general announcement to QA.
>>>
>>> NOTE: the staging web site -- http://ooo-site.staging.apache.org/ --
>> allows
>>> for +Indexes automatically so displays can be  misleading in that
>>> environment. Our default setup for -- http://www.openoffice.org/ -- does
>>> not.
>>>
>>> We should probably request that infra setup both these servers the same.
>>>
>>>
>> Kay;
>>
>> Just tried to check out ooo-site repo in preparation for completing the
>> download of all the Impress test cases and ran into a problem. You have
>> a number of files that include an * in the filename. This is no-no on
>> windows and causes a corrupt working copy on Windows that can not be
>> used. Can you update the ooo-site repo and replace those 1/2 dozen or so
>> files with * in the names so that I can check out a new working copy?
>>
>
> ​Yes, I will do that.
Thanks Kay. A closer look at the repo shows somewhere around 2 dozen
files that have * in the file name.

> ​
>
>
>>
>> Also a process question. Why did you chose to put all the tests in a
>> single directory rather than breaking it down by application the way
>> they were on the testlink site?
>
>
> ​An oversight on my part, but as I got into this, I did see there was a LOT
> of overlap, with the former QA folks establishing categories for some very
> specific areas. We can probably restructure this new area just based on
> file names and move things around. I discovered on the original TestLink
> site that there were MANY fine-grained categorizations that we probably
> don't need.
>
> ​
>
>
>> The process engineer in me says that it
>> would be cleaner to do it by application so that a volunteer working on
>> Writer doesn't have to wade through tests that do not apply to them to
>> find the Writer specific ones.
>>
>
> ​I thought perhaps the file names themselves would suffice for determining
> categories. In any case, please feel free to organize this area further. I
> would think subareas for Wrtier, Calc, Impress, Database, Drawing would be
> enough -- or not.

Once  I get a clean checkout of the repo I will take a closer look at
possibilities for restructuring it a bit.

Regards
Keith

> ​
>
>
>>
>> Regards
>> Keith​
>
>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Kay Schenk-2
On Mon, Apr 2, 2018 at 4:18 PM, Keith N. McKenna <[hidden email]>
wrote:

> On 4/2/2018 6:41 PM, Kay Schenk wrote:
> > On Mon, Apr 2, 2018 at 3:07 PM, Keith N. McKenna <
> [hidden email]>
> > wrote:
> >
> >> On 3/30/2018 3:15 PM, Kay Schenk wrote:
> >>> I've committed changes to the QA area complete with the "index"
> >> capability
> >>> of the new test case area. I'll be working on additional changes to the
> >> QA
> >>> area over the next few days before a general announcement to QA.
> >>>
> >>> NOTE: the staging web site -- http://ooo-site.staging.apache.org/ --
> >> allows
> >>> for +Indexes automatically so displays can be  misleading in that
> >>> environment. Our default setup for -- http://www.openoffice.org/ --
> does
> >>> not.
> >>>
> >>> We should probably request that infra setup both these servers the
> same.
> >>>
> >>>
> >> Kay;
> >>
> >> Just tried to check out ooo-site repo in preparation for completing the
> >> download of all the Impress test cases and ran into a problem. You have
> >> a number of files that include an * in the filename. This is no-no on
> >> windows and causes a corrupt working copy on Windows that can not be
> >> used. Can you update the ooo-site repo and replace those 1/2 dozen or so
> >> files with * in the names so that I can check out a new working copy?
> >>
> >
> > ​Yes, I will do that.
> Thanks Kay. A closer look at the repo shows somewhere around 2 dozen
> files that have * in the file name.
>
> > ​
> >
> >
> >>
> >> Also a process question. Why did you chose to put all the tests in a
> >> single directory rather than breaking it down by application the way
> >> they were on the testlink site?
> >
> >
> > ​An oversight on my part, but as I got into this, I did see there was a
> LOT
> > of overlap, with the former QA folks establishing categories for some
> very
> > specific areas. We can probably restructure this new area just based on
> > file names and move things around. I discovered on the original TestLink
> > site that there were MANY fine-grained categorizations that we probably
> > don't need.
> >
> > ​
> >
> >
> >> The process engineer in me says that it
> >> would be cleaner to do it by application so that a volunteer working on
> >> Writer doesn't have to wade through tests that do not apply to them to
> >> find the Writer specific ones.
> >>
> >
> > ​I thought perhaps the file names themselves would suffice for
> determining
> > categories. In any case, please feel free to organize this area further.
> I
> > would think subareas for Wrtier, Calc, Impress, Database, Drawing would
> be
> > enough -- or not.
>
> Once  I get a clean checkout of the repo I will take a closer look at
> possibilities for restructuring it a bit.
>

​OK, I think the filenames are fixed now. Bad commit the first time I guess.
Great if you could help with the restructuring. Please keep in mind that
this is not ALL the TestLink files. I need to see what we're missing and
want to have at this point.



>
> Regards
> Keith
> > ​
> >
> >
> >>
> >> Regards
> >> Keith​
> >
> >
> >>
> >>
>
>
>


--
----------------------------------------------------------------------
MzK

"Less is MORE."
Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Keith N. McKenna
In reply to this post by Keith N. McKenna
On 4/2/2018 7:29 PM, Kay Schenk wrote:
> OK, I think the filenames are fixed now. Bad commit the first time I guess.
> Great if you could help with the restructuring. Please keep in mind that
> this is not ALL the TestLink files. I need to see what we're missing and
> want to have at this point.
> ​
Thanks Kay. Doing a new checkout now. Hopefully this should do it. Will
let you know the outcome.

Keith


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Keith N. McKenna
On 4/2/2018 8:07 PM, Keith N. McKenna wrote:

> On 4/2/2018 7:29 PM, Kay Schenk wrote:
>> OK, I think the filenames are fixed now. Bad commit the first time I guess.
>> Great if you could help with the restructuring. Please keep in mind that
>> this is not ALL the TestLink files. I need to see what we're missing and
>> want to have at this point.
>> ​
> Thanks Kay. Doing a new checkout now. Hopefully this should do it. Will
> let you know the outcome.
>
> Keith
>
Checkout completed with no errors. Thank you very much for your assistance.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Keith N. McKenna
In reply to this post by Keith N. McKenna
On 4/2/2018 7:29 PM, Kay Schenk wrote:
<snip>
> ​OK, I think the filenames are fixed now. Bad commit the first time I guess.
> Great if you could help with the restructuring. Please keep in mind that
> this is not ALL the TestLink files. I need to see what we're missing and
> want to have at this point.

Another Question. When you downloaded the files from the testlink site
did you filter for only manual execution? I notice that your initial
directory was for ManualExecution.

Regards
Keith


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [WEBSITE] QA area changes, and differences between staging and production

Kay Schenk-2
On Tue, Apr 3, 2018 at 1:59 PM, Keith N. McKenna <[hidden email]>
wrote:

> On 4/2/2018 7:29 PM, Kay Schenk wrote:
> <snip>
> > ​OK, I think the filenames are fixed now. Bad commit the first time I
> guess.
> > Great if you could help with the restructuring. Please keep in mind that
> > this is not ALL the TestLink files. I need to see what we're missing and
> > want to have at this point.
>
> Another Question. When you downloaded the files from the testlink site
> did you filter for only manual execution? I notice that your initial
> directory was for ManualExecution.
>
> Regards
> Keith
>

​Hi Keith --
I followed the instructions I posted on the QA list In February --



https://lists.apache.org/thread.html/fdca925316308fda4f4faed31276f79c4e48baf4badea8842f452f4d@%3Cqa.openoffice.apache.org%3E

​The "browse cases" give you viewing of manual test cases. The new
directory I created under --
http://www.openoffice.org/qa/testcase/ManualTesting

are written test cases previously used in QA "manual" testing.

If you're finding ManualExecution on TestLink(?), this is an area that I
did not use.

There is a LOT more cleanup and documentation of process to do at this
point, and I now see the new area is NOT available for public viewing as it
was on March 30, so I need to investigate the cause.

Hope this helps.


--
----------------------------------------------------------------------
MzK

"Less is MORE."