On Thu, Nov 27, 2008 at 11:21 AM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> I'm keen to try to find some proper ways to fix this, but before I go
> too deep into the bowels of Django's testing framework, I was
> wondering what would be the criticisms you'd have about the "solution"
> I came up
I'm keen to try to find some proper ways to fix this, but before I go
too deep into the bowels of Django's testing framework, I was
wondering what would be the criticisms you'd have about the "solution"
I came up with (at the start of this thread)? It sort of works without
patching Django, but is
I took a similar path. I cloned the run_tests function from
django.tests.simple.py and put it in my project directory as
test_setup.py while adding this near the top of the function:
if settings.TEST_APPS:
settings.INSTALLED_APPS += settings.TEST_APPS
That at least allows me to define
On Nov 27, 10:55 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Thu, Nov 27, 2008 at 8:33 AM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> > So, all this works pretty well. The 'fakeapp' app is loaded
> > dynamically, tables are created and the FakeItem model can be use in
> > my
On Thu, Nov 27, 2008 at 8:33 AM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> So, all this works pretty well. The 'fakeapp' app is loaded
> dynamically, tables are created and the FakeItem model can be use in
> my tests.
>
> But it feels dirty. The dynamically created tables can potentially
>
On Tue, Nov 25, 2008 at 9:18 PM, Tim Chase
<[EMAIL PROTECTED]> wrote:
>
>> Check out django.contrib.auth.tests.views.py.
>
> Is there some master index of documentation for "if you want to
> test X, see Y.py or http://Z for an example of how to do it"?
> where X is any of a number of Django
On Nov 25, 11:18 pm, Tim Chase <[EMAIL PROTECTED]> wrote:
> > Check out django.contrib.auth.tests.views.py.
>
> Is there some master index of documentation for "if you want to
> test X, see Y.py or http://Z for an example of how to do it"?
> where X is any of a number of Django features such as
> Check out django.contrib.auth.tests.views.py.
Is there some master index of documentation for "if you want to
test X, see Y.py or http://Z for an example of how to do it"?
where X is any of a number of Django features such as models,
views, templates, middleware, filters, template-tags,
On Tue, Nov 25, 2008 at 9:05 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> On Nov 25, 11:01 pm, Julien Phalip <[EMAIL PROTECTED]> wrote:
>> On Nov 25, 10:56 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
>> wrote:
>>
>>
>>
>> > On Tue, 2008-11-25 at 20:47 +0900, Russell Keith-Magee wrote:
>> > >
On Nov 25, 10:56 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Tue, 2008-11-25 at 20:47 +0900, Russell Keith-Magee wrote:
> > On Tue, Nov 25, 2008 at 8:40 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > I've got a view which uses a different template depending on an
On Nov 25, 11:01 pm, Julien Phalip <[EMAIL PROTECTED]> wrote:
> On Nov 25, 10:56 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
>
>
>
> > On Tue, 2008-11-25 at 20:47 +0900, Russell Keith-Magee wrote:
> > > On Tue, Nov 25, 2008 at 8:40 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> > > >
On Tue, 2008-11-25 at 20:47 +0900, Russell Keith-Magee wrote:
> On Tue, Nov 25, 2008 at 8:40 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I've got a view which uses a different template depending on an input
> > parameter. For example:
> >
> > def my_view(request, theme):
> >
Excellent! Thanks for the tip Russ ;)
On Nov 25, 10:47 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Tue, Nov 25, 2008 at 8:40 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> > Hi,
>
> > I've got a view which uses a different template depending on an input
> > parameter. For
On Tue, Nov 25, 2008 at 8:40 PM, Julien Phalip <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've got a view which uses a different template depending on an input
> parameter. For example:
>
> def my_view(request, theme):
>...
>return render_to_response('my_app/%s/page.html' %s theme, {...})
>
>
Done. For those following along, here's the link:
http://www.djangosnippets.org/snippets/1186/
On Nov 13, 10:17 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Fri, Nov 14, 2008 at 12:13 PM, Erik <[EMAIL PROTECTED]> wrote:
>
> > In case there are others following this topic, I have
On Fri, Nov 14, 2008 at 12:13 PM, Erik <[EMAIL PROTECTED]> wrote:
>
> In case there are others following this topic, I have the test system
> working. I ended up putting a couple of functions in the contrib
> folder of my django installation under the mako_django folder. The
> functions emulate
In case there are others following this topic, I have the test system
working. I ended up putting a couple of functions in the contrib
folder of my django installation under the mako_django folder. The
functions emulate the behavior of the instrumented_test_render and
run_tests functions from
Thanks! I'll look into this. If anyone is interested in the outcome
I'll submit a patch to the mako_django package I'm using. Drop a
reply here if you're interested in the results.
On Nov 12, 6:24 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Thu, Nov 13, 2008 at 9:58 AM, Erik
On Thu, Nov 13, 2008 at 9:58 AM, Erik <[EMAIL PROTECTED]> wrote:
>
> I am involved in a project that's using django with the mako_django
> package for template rendering. I'm working on the unit tests, but
> I'm running into the problem that the context and template are not
> returned after a
My fixtures won't load unless I name them "initial_data". What is the
reason for this?
On Aug 26, 7:02 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Tue, Aug 26, 2008 at 11:18 PM, dchandek <[EMAIL PROTECTED]> wrote:
>
> > After several iterations of running tests on an application
On Tue, 2008-09-02 at 18:45 -0700, ballparkfh wrote:
> My fixtures won't load unless I name them "initial_data". What is the
> reason for this?
Based on the complete lack of example code you've provided, it's
difficult to tell. Perhaps post a short example of your TestCase-derived
class so we
On Tue, Aug 26, 2008 at 11:18 PM, dchandek <[EMAIL PROTECTED]> wrote:
>
> After several iterations of running tests on an application (manage.py
> test myapp), I have these observations which are not really clear in
> the documentation:
>
> 1. All initial_data fixtures (not just those for the
One more:
4. django.test.TestCase effectively reloads initial_data fixtures with
every test because it calls the flush command.
--David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
On Jul 21, 2:39 am, "Gwyn Evans" <[EMAIL PROTECTED]> wrote:
> Just wondered if I'm missing something, or if it's just not been an
> issue to anyone...
>
> Looking at the DB testing docs, it seems that it tries to use a
> 'TEST_', for testing. This is a bit of a problem with Oracle,
> where a new
Thanks Russ I'll try what you suggested, I was hoping there was
another way besides how I was trying to do it.
Many people compare Django to rails which, independent of any other
connotations, does seem to expose a difference in testing. It's been
almost a year since I worked with rails, and the
On Mon, Jul 14, 2008 at 9:28 AM, jawspeak <[EMAIL PROTECTED]> wrote:
>
> I'm not experienced in python but coming from Java I'm having a hard
> time being forced to put all my tests for an app in one file.
...
> It really bothers me that I don't know how to automatically include
> every file
Hey I am able to run the test by using :
class IndustryTest(TestCase):
fixtures = ['/fixtures/initial_data.xml']
def setUp(self):
self.client = Client()
response =self.client.post('/ibms/login/',
{'username':'laspal', 'password':'abcd'})
def test_addIndustry( self):
Hey I am able to run the test by using :
class IndustryTest(TestCase):
fixtures = ['/fixtures/initial_data.xml']
def setUp(self):
self.client = Client()
response =self.client.post('/ibms/login/',
{'username':'laspal', 'password':'abcd'})
def test_addIndustry( self):
On Thu, Jul 3, 2008 at 2:18 PM, laspal <[EMAIL PROTECTED]> wrote:
>
> Hi,
> Thanks for the help but still I am not able to login in my test
> client..
>
> here is the code:
>
> from django.test import TestCase
> from django.test.client import Client
>
> class IndustryTest(TestCase):
>fixtures
Hi,
Thanks for the help but still I am not able to login in my test
client..
here is the code:
from django.test import TestCase
from django.test.client import Client
class IndustryTest(TestCase):
fixtures = ['/fixtures/initial_data.xml']
def setUp(self):
self.client =
On Wed, Jul 2, 2008 at 10:14 PM, Norman Harman <[EMAIL PROTECTED]> wrote:
>
> Test system creates a new test database from scratch every time it is
> run. manage.py loaddata has NO effect on test.
>
> I could be wrong but I don't believe test runner automatically loads the
> fixture
You can check my dump of manage.py test (ran as root) here;
http://dpaste.com/60433/
As you can see the fixture load runs OK... and I even got a couple of
errors on the load process! That sure confirms the fixtures load ;-)
Tests run fine though.
On Jul 2, 4:14 pm, "Norman Harman" <[EMAIL
laspal wrote:
> Hi,
> I have created initial_data.xml using dumpdata and
> """manage.py loaddata initial_data.xml""" gives me no error.
> but still I am not able to login using setUp().. and this is
> essential as all my views functions required login..
>
> here is my test file:
>
> import
Hi,
I have created initial_data.xml using dumpdata and
"""manage.py loaddata initial_data.xml""" gives me no error.
but still I am not able to login using setUp().. and this is
essential as all my views functions required login..
here is my test file:
import unittest
from django.test import
> How do I create username and password for the test database.
What I do is either create a test user on SetUp(), or put that
username inside the "initial_data" fixture, which loads automatically
when Django creates the test DB...
HTH,
Carlos
How do I create username and password for the test database.
On Jul 1, 2:24 pm, Julien <[EMAIL PROTECTED]> wrote:
> Hi,
>
> If you're using the SVN version you can try:
>
> >>> c = Client()
> >>> c.login(username='fred', password='secret')
>
> More info
Hi,
If you're using the SVN version you can try:
>>> c = Client()
>>> c.login(username='fred', password='secret')
More info here: http://www.djangoproject.com/documentation/testing/
On Jul 1, 5:51 pm, laspal <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am writing the test case but I am getting
Hi Russ,
thanks for your answer. I will open a ticket and attach the test case.
regards,
peschler
On 10 Jun., 15:45, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Tue, Jun 10, 2008 at 6:53 AM, peschler <[EMAIL PROTECTED]> wrote:
>
> > I'm currently facing a weird problem with the
On Tue, Jun 10, 2008 at 6:53 AM, peschler <[EMAIL PROTECTED]> wrote:
>
> I'm currently facing a weird problem with the testing framework after
> updating to the latest trunk version of the newforms-admin branch. I
> have written a small example and a unittest to explain the issue and
> to show
On Tue, May 20, 2008 at 9:19 PM, Julien <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a site where pretty much all views (except for register, login
> and logout) require the user to log in. Now that the number of views
> has grown I'd like to test that I didn't forget to protect them with
> the
In another thread [1] James Bennett suggested to use a middleware to
require login for all views. That is indeed a very simple and elegant
way. Here's the code I ended up with:
from django.contrib.auth.decorators import login_required
from django.conf import settings
public_paths =
Ah I know where I have gone wrong now. I should have specified q
instead of query in my test function.
Its so obvious now. I think I spent too long looking at test
function, it made my eyes blurry.
Thanks
Tony
On Apr 7, 10:47 am, Tony <[EMAIL PROTECTED]> wrote:
> I have developed an
Malcolm, thanks for the answer. I should have better read src of
client.py.
default for query environment can be overridden like so:
c = Client(REMOTE_ADDR ='127.0.0.1') - this solves my problem!
> Work out which standards are relevant. If REMOTE_ADDR *must* be supplied
> by all web servers,
On Fri, 2008-01-04 at 14:30 -0800, Thomas wrote:
> I am testing django.contrib.comments with django.test.client that does
> not provide request.META['REMOTE_ADDR'] and therefore dies at
> http://code.djangoproject.com/browser/django/trunk/django/contrib/comments/views/comments.py#L252
>
> There
Responding to myself:
I choosed solution 2 (parse HTML form) with the help of ClientForm:
http://www.djangosnippets.org/snippets/467/
Comments welcome
Am Freitag, 16. November 2007 13:03 schrieb Thomas Guettler:
> Hi,
>
> my has a lot of input widgets which are build from several
>
You could also just use a loopback filesystem (essentially a fixed size file
mounted as its own filesystem). Been years since i've used this, so cant
give any specific help, but should be simper than ramdisks.
Tom
On 27/10/2007, Faheem Mitha <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi,
>
> Here is a
On 9/17/07, john <[EMAIL PROTECTED]> wrote:
>
> coming from Rails so any help appreciated
>
> 1) I realize you can use doctests or unit tests - but is one
> recommended over the other ?
Not particularly. They both have their advantages. doctests are very
easy to set up, and are very easy to read
[ Sorry for long delay, django is one of my "also projects" ]
On Aug 11, 11:15 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> As for how to fix this problem, I have two suggestions.
>
> 1) Are you sure you can't just fix this with a static fixture?
Yes, that should work just fine. The
On 8/11/07, Chris Green <[EMAIL PROTECTED]> wrote:
>
> On Aug 9, 7:55 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> wrote:
> > On 8/9/07, Chris Green <[EMAIL PROTECTED]> wrote:
> > > 2) Setting up users/groups/users manually in the runner gets blown
> > > away by the TestCase architecture.
On Aug 9, 7:55 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 8/9/07, Chris Green <[EMAIL PROTECTED]> wrote:
> > 1) initial_data has bitten me not realizing it was synced in
> > production each time.
> There is an argument to be made that initial_data for a model should
> only be
On 8/9/07, Chris Green <[EMAIL PROTECTED]> wrote:
>
> 1) initial_data has bitten me not realizing it was synced in
> production each time. I think that initial_data should only get
> inserted if you have an empty new database. Perhaps things synced
> each time should be called
Для тестов существуют модули doctest и unittest, попробуй почитать
документацию :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
the dict was supposed to be passing in the logged user, though I am
starting to think I don't need to pass anything as long as I can get
the session set.
Another developer in the office wrote the auth code so it took me a
bit to get a handle on just what it was doing.
I am thinking if i get the
On 6/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Jeremy,
>Thanks for the response.
>
> to be more clear maybe -
>i was actually trying to pass the dictionary as part of the request
> object - since the view looks for the logged participant in the
> request from the page.
>
>
Jeremy,
Thanks for the response.
to be more clear maybe -
i was actually trying to pass the dictionary as part of the request
object - since the view looks for the logged participant in the
request from the page.
what if my view does not take a qstring? I need to pass it some
pieces in
On 6/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
...
> response = self.client.get('/broadcasts/new/',
> {'loggedParticipant': participant} )
It's not clear to me what the dictionary there is meant to do. That
dictionary is passed as the querystring, *not* as the session.
Also,
On 4/12/07, Brian Luft <[EMAIL PROTECTED]> wrote:
>
> If I remember correctly, my problem was that the JSON serializer was
> bombing out when encountering float fields. I didn't report it
> directly because I thought I had remembered seeing others report
> similar problems. It was probably a
If I remember correctly, my problem was that the JSON serializer was
bombing out when encountering float fields. I didn't report it
directly because I thought I had remembered seeing others report
similar problems. It was probably a late night and I got around it by
opting for XML formatting.
On 4/12/07, Merric Mercer <[EMAIL PROTECTED]> wrote:
>
> I tried to run the dumpdata command because I'd read that this did much
> of the work for me but I received the following error message
>
> >>C:\>manage.py dumpdata promotions
> Unable to serialize database: Table_Code matching query does
On 4/12/07, Brian Luft <[EMAIL PROTECTED]> wrote:
>
> I've run into problems as well with the fixture functionality. The
> short of it is that this is a new feature to the framework and likely
> the kinks will be worked out in the coming weeks.
Have you reported these problems? I am aware of
I've run into problems as well with the fixture functionality. The
short of it is that this is a new feature to the framework and likely
the kinks will be worked out in the coming weeks.
In the meantime you might check out one of these as a workable
temporary solution:
Thanks for the suggestion Grig.
I'll give it a shot on Monday.
/Paul
On 3/10/07, Grig <[EMAIL PROTECTED]> wrote:
>
> Paul -- have you tried running the Selenium RC server non-
> interactively, then interacting with it via one of the languages it
> supports? Python for example, since you're doing
Paul -- have you tried running the Selenium RC server non-
interactively, then interacting with it via one of the languages it
supports? Python for example, since you're doing Django development.
Look in the python sub-directory of the selenium-rc distribution, and
modify the test_google.py
Thanks Jeremy.
> I think, since the idms pattern is not being handled by an include,
> you may want this:
> (r'^idms/$',"idms.general.views.idms" ),
> (note the "$" at the end of the pattern).
I made the change and tried again but it didn't make a difference.
Cheers,
/Paul
On 3/9/07, Paul Childs <[EMAIL PROTECTED]> wrote:
...
> (r'^ssi/', include('idms.ssi.urls')),
>
> (r'^idms/',"idms.general.views.idms" ),
>
I think, since the idms pattern is not being handled by an include,
you may want this:
(r'^idms/$',"idms.general.views.idms" ),
(note the "$" at the
On Fri, 2007-03-09 at 13:57 +, Paul Childs wrote:
> Thanks again Malcolm.
>
> It looks like this is starting to get beyond my comfort level. Given
> that and my time constraints, it looks like Selenium is a non-starter.
> I guess I'll just have to rely on humans to do that part of the
>
Thanks again Malcolm.
It looks like this is starting to get beyond my comfort level. Given
that and my time constraints, it looks like Selenium is a non-starter.
I guess I'll just have to rely on humans to do that part of the
testing. The Selenium IDE worked fine but unfortunately it's not
On Fri, 2007-03-09 at 12:59 +, Paul Childs wrote:
> Thanks for the response Malcom...
>
> > Does the same URL work if you aren't using Selenium? I'm trying to trim
> > down the problem to something smaller.
> When I type http://127.0.0.1:8000/idms/ into the address bar I do not
> get a
Thanks for the response Malcom...
> Does the same URL work if you aren't using Selenium? I'm trying to trim
> down the problem to something smaller.
When I type http://127.0.0.1:8000/idms/ into the address bar I do not
get a Django error and the proper page is rendered.
> I *suspect* there is a
On Thu, 2007-03-08 at 19:46 +, Paul Childs wrote:
[...]
> Then I get this Django Error message in the browser...
>
> TypeError at http://127.0.0.1:8000/idms/
> unpack non-sequence
> Request Method: GET
> Request URL: http://127.0.0.1:8000http://127.0.0.1:8000/idms/ <
> THIS IS
> Can you provide a few more clues, please? In particular, what exception
> is being raised. If we know what part of the code is involved, it will
> be easier to try and work out the differences.
> If you can reduce the behaviour to a simple (only a few lines) example,
> that would be great, too.
On Wed, 2007-03-07 at 02:24 -0800, Lawrence Oluyede wrote:
> I'm having some problems with the same codebase tested with Python 2.5
> and previous versions. With Python 2.5 the tests pass smoothly but
> with 2.4 and 2.3 they "explode". The problem seems to arise when the
> application raises an
On 10/12/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
>
> Is there any interest in a little testing framework that mocks out
> django to make it relatively easy to unit test views code?
A nice little testing framework already exists. It contains the
ability to test URL dispatch, view execution,
201 - 273 of 273 matches
Mail list logo
