Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bk8mj-0006Nn-RD for pgadmin-hackers@arkaria.postgresql.org; Wed, 14 Sep 2016 11:55:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bk8mi-0006RU-Tz for pgadmin-hackers@arkaria.postgresql.org; Wed, 14 Sep 2016 11:55:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bk8mi-0006RN-Ez for pgadmin-hackers@postgresql.org; Wed, 14 Sep 2016 11:55:24 +0000 Received: from mail-it0-x22d.google.com ([2607:f8b0:4001:c0b::22d]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bk8md-00049w-N6 for pgadmin-hackers@postgresql.org; Wed, 14 Sep 2016 11:55:23 +0000 Received: by mail-it0-x22d.google.com with SMTP id r192so39710354ita.0 for ; Wed, 14 Sep 2016 04:55:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JtzZz/LtDMZIPF7Vi6AQ09ZUxgGFgyJzYgW4f9jPhTQ=; b=uXsWDkWfeQMM5Je9PJlJe9K6jTsPOz2Jtr8+bodzYroq29MotBNmpAtebnbNaTQ/1Q k+0QPurzxMajCx32RvthUOOONNvyVtFGS7D7jh1Ce36LtlZPKJBOlt/OAp/3saVI1HYv AKFej5Hwv5+Sgc6rfTCc/b5BJNT+pBgcJrCgr+uqKFOM0HhVKFPSd9s5YW6L1PXrd/Bj y+d9Qk7hFwXxaZTeoRM3e44CKn8AYgXwNVlyXTYE6bCI9xKwssdMy/bVlAbWuLfK0dt5 7rnezFROd5AYSd0RkS/G++88vZp3Hc95SYlFTNsba4KQEuwig8qbeopRThr7f/edLL7I +pFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JtzZz/LtDMZIPF7Vi6AQ09ZUxgGFgyJzYgW4f9jPhTQ=; b=hVwiJ1guRlkuPC63RWKCWN9aGKlAilp4akI32hpzAFwqF59t5Ht9OprdnNk/OEHkCA xJV8a13QxFP7kN/wVrmuLJSVANpISAHXU4PAI61lDt7t+uz8GtOppiufXcVtS29a3Ye5 ZPvZkafQEVPaMPiEtJw3N94hw6Jcmx5yRwvb4NFFc3YwdLcp3bNXPf/3KO6QjxZB7XyM qVPT+Fgo0jDXpH57z5DS1KYn79YfWimAP+CqHGCOZSj1YnRCOQm1dbmlze2H6OIPz2EI VBB5l3x6MIqqXefMScqVW/1aXPIAMSvKwQWb7TLYgUARiZeRD39Tf+5Nz6kL5u7m/376 evUA== X-Gm-Message-State: AE9vXwMAt4ks+ujHuUVKIMDZK7aar69FzC6n29r6u1MKLWkqfksUoPqNhfSdVnaUyYO9MA5rySET/JHoHBtyO4kVQ0khyaX+xHNheEe5elt80n9Gonp2iTpPxd9rsnD4K4LNBgAqKBqLt0oa8dtsbUZrnrRoTn9bCq8Mia5CJkv+FvPpa4bmRPoet7PQHqGLXmLOqX3kzg== X-Received: by 10.107.135.67 with SMTP id j64mr5265610iod.21.1473854117558; Wed, 14 Sep 2016 04:55:17 -0700 (PDT) Received: from mail-it0-f49.google.com (mail-it0-f49.google.com. [209.85.214.49]) by smtp.gmail.com with ESMTPSA id e8sm3742330itc.15.2016.09.14.04.55.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Sep 2016 04:55:16 -0700 (PDT) Received: by mail-it0-f49.google.com with SMTP id 186so19529502itf.0 for ; Wed, 14 Sep 2016 04:55:16 -0700 (PDT) X-Received: by 10.107.170.168 with SMTP id g40mr5446888ioj.173.1473854116369; Wed, 14 Sep 2016 04:55:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.1.203 with HTTP; Wed, 14 Sep 2016 04:55:15 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Wed, 14 Sep 2016 12:55:15 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: pgAdmin IV: Unittests-drop objects functionality To: Navnath Gadakh Cc: pgadmin-hackers , Kanchan Mohitey Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.1 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org Hi On Tue, Sep 13, 2016 at 3:39 PM, Navnath Gadakh wrote: > Hi Dave, > Please find the patch for drop objects functionality for test > framework. > Now, test framework is able to drop all objects(like server, database, > schema, etc.) which are created during test suite execution. Code included > in the patch is only for server and database node. If everything goes fine > will send next patch with the remaining nodes in a single patch. > > The following files are also affected by the new changes: > web/setup.py, > web/config.py, > regression/test_advanced_config.json.in > > > To run the test suite follow the commands > 1. python runtionregress/ests.py --pkg browser.server_groups.servers > 2. python regression/runtests.yp --pkg > browser.server_groups.servers.databases > > > Note: Please do not run test suite for all nodes (python > regression/runtests.py) as code modifications have not been done yet. I'm happy with this in general, except the changes in setup.py - Let's use the names PGADMIN_SETUP_EMAIL and PGADMIN_SETUP_PASSWORD for the envvars. - Why are you setting the username and password in the environment after prompting the user for them? I can't see why you're doing that, and it's almost certainly a security issue. -- Dave Page VP, Chief Architect, Tools & Installers EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company Blog: http://pgsnake.blogspot.com Twitter: @pgsnake -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers