On 2015-11-04 18:39, Gergely Polonkai wrote: > An even more fine grained solution may be using an HTML parser like > beautifulsoup. However, if your site's functionality depends on > client side features like JavaScript, Selenium may be a better > alternative.
My code doesn't rely on any JavaScript and I was hoping to keep everything to mostly-Django without the need to drive an actual web-browser like Selenium would do. Sorry, should have mentioned that in my initial post. My hope was for 1) something like "assertFormUsed()" akin to "assertTemplateUsed()" to check whether a form was rendered as part of a given template, and 2) the ability for to know what a form/formset's rendered field-names would be so I don't have to hard-code them in the post(). When using a form-set, the field-names get augmented with the form-set ID/number which can make it more of a challenge to identify the field-names. If there's some other functionality that would help with this instead of how I was imagining it, I'm open to suggestions there. Thanks, -tkc -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/20151104155535.45ead6a2%40bigbox.christie.dr. For more options, visit https://groups.google.com/d/optout.
