Sorry if I confused people... I'm still looking for some feedback.
Really, I guess I just want to streamline CSS/layout/language/browser
testing so problems that commonly occur aren't discovered on the final
round of staging testing.
I imagine a test series like:
[ {
series_name: payroll_screens,
urls: [ url1,url2... ]
fixtures: payroll.json, employees.json
},
...
]
And through a test url that puts a 'next/prev' widget somewhere like a
top bar, iterates through the urls (in an iframe?) while loading and
unloading fixtures.
Is this a really weird thing to want to do? You can TDD almost
everything else in django through TestClient except for the end result
of how stuff looks.
Jennifer
On Jan 4, 6:21 pm, Jennifer Bell <jenniferlia...@yahoo.ca> wrote:
> OK, to elaborate: I have a open source project with consistent pain
> points around css and browser testing. Example concrete issues for
> this project are a) multi-language support, as varying text length
> will often throw off the aesthetics of the layout, and b) recently, a
> mysterious failure in geodjango google-map drawing where in some
> corner-cases, the map silently fails to draw.
>
> Really, I'm looking for a framework for a human tester to be able to
> look at a sequence of html pages generated with different test data in
> the database. I want the tester to be able make a 'pretty/ugly/
> horribly wrong' call without having to do a bunch of clicking or data
> entry. Ideally, they would just click 'next' on some widget, which
> would pull up the next URL/test db combination.
>
> Jennifer
>
> On Jan 4, 5:18 pm, Nick Stinemates <nstinema...@gmail.com> wrote:
>
> > Can you elaborate a bit?
>
> > Are you interested in having the ui render and generate a screen shot
> > for human review? That's how I interpreted your question. If that's
> > the case, look in to generating a screenshot by leveraging a tool that
> > generates a png from HTML.
>
> > I am eager to hear what others think.
>
> > Nick
>
> > On Tuesday, January 4, 2011, Jennifer Bell <jenniferlia...@yahoo.ca> wrote:
> > > Hi,
>
> > > I'm trying to figure out the best way of doing something.... I'd like
> > > to partially automate staging testing by generating a sequence of
> > > human verifiable views, with the goal of making sure my app views/css/
> > > 3rd-party javascript etc. are drawing the way they ought to in more
> > > complicated scenarios. While back end code can easily be tested
> > > with TestClient, failures in the 'final mile' of rendering are really
> > > annoying.
>
> > > It would be nice to have a 'view test mode' that allows a tester to
> > > click through a series of database configuration / URL pairs in a
> > > relatively painless way.
>
> > > Is there a standard way of doing this, or any existing modules I could
> > > use to achieve this?
>
> > > Jennifer
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Django users" group.
> > > To post to this group, send email to django-us...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > django-users+unsubscr...@googlegroups.com.
> > > For more options, visit this group
> > > athttp://groups.google.com/group/django-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
