[Xerte-dev] Re: Testing

[Kemp Johnathan]

Am I right in assuming that at present you are testing the code that
delivers the XOT web experience, rather than the specific model files and
template.xwd, both of which will be affected by the move to modularisation,
and that the testing of this will come after you are happy that the XOT
interface is working?

If so do you have a feel for when you will want the work on the model files
finished? The are almost there now. I have a little bit of tidying up to do
and I need to add Ron's feature requests to the Hotspot Image Connector but
then they should be ready for testing.

If there is a little more time I will also prepare my Inventory page for
inclusion and I would also like to take a stab at creating a Developer mode
version of the menu page.

Kind regards

Johnathan

On 5 March 2012 10:10, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:

> Let’s use the issues on xerteonlinetoolkits at google code, but if you
> have time fix all the obvious ones first…
>
>
>
> *From:* xerte-dev-bounces at lists.nottingham.ac.uk [mailto:
> xerte-dev-bounces at lists.nottingham.ac.uk] *On Behalf Of *Julian Tenney
> *Sent:* 05 March 2012 10:09
>
> *To:* For Xerte technical developers
> *Subject:* [Xerte-dev] Re: Testing
>
>
>
> Run it on xampp for now, I’d say a beta version would be when it works
> seamlessly on xampp…
>
>
>
> *From:* xerte-dev-bounces at lists.nottingham.ac.uk [mailto:
> xerte-dev-bounces at lists.nottingham.ac.uk] *On Behalf Of *David Goodwin
> *Sent:* 05 March 2012 10:08
> *To:* For Xerte technical developers
> *Subject:* [Xerte-dev] Re: Testing
>
>
>
>
>
> On 5 Mar 2012, at 10:05, Julian Tenney wrote:
>
>
>
> Hiya,
>
>
>
> How best to proceed with the testing: I can also install it now, and
> create and preview a LO, but there are a load of errors on publishing,
> opening the properties window, and so on. Is it worth Pat /David going
> through an putting as much of this right as possible before we start really
> testing everything, as it seems daft logging bugs when there are so many
> that are easily identified.
>
>
>
>
>
> That requires me to install a test instance somewhere…
>
>
>
> What do you think?
>
>
>
> Also, once we’ve got something that looks like it might be ready for
> closer scrutiny, how to record the bugs? Shall we use the google code
> issues?
>
>
>
>
>
> It would make sense - as in at least there would be some sort of list of
> outstanding things / things that need fixing...
>
>
>
> David
>
>
>
> Pale Purple Ltd.  (Company No: 5580814)
>
> 'Business Web Application Development and Training in PHP'
>
>
>
> http://www.palepurple.co.uk
>
> Office: 0845 0046746     Mobile: 07792380669
>
>
>
> Follow us on Twitter: @PalePurpleLtd
>
>
>
>  This message and any attachment are intended solely for the addressee and
> may contain confidential information. If you have received this message in
> error, please send it back to me, and immediately delete it. Please do not
> use, copy or disclose the information contained in this message or in any
> attachment. Any views or opinions expressed by the author of this email do
> not necessarily reflect the views of the University of Nottingham.
>
> This message has been checked for viruses but the contents of an
> attachment may still contain software viruses which could damage your
> computer system: you are advised to perform your own checks. Email
> communications with the University of Nottingham may be monitored as
> permitted by UK legislation.
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>
> This message and any attachment are intended solely for the addressee and
> may contain confidential information. If you have received this message in
> error, please send it back to me, and immediately delete it.   Please do
> not use, copy or disclose the information contained in this message or in
> any attachment.  Any views or opinions expressed by the author of this
> email do not necessarily reflect the views of the University of Nottingham.
>
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20120305/2a448a3f/attachment-0001.html>