Re: Setting up a system for testing by users (tables are tables?)

2018-08-14 Thread guettli


Am Montag, 13. August 2018 18:12:03 UTC+2 schrieb Mikhailo Keda:
>
> 1. take a dump of production db
> 2. remove/anonymize all sensitive or unneeded data (you can use django 
> admin or sql or python script)
> 3. reduce amount of data if needed
> 4. take a git branch with fixes 
> 5. make sure there are no sensitive data in your code
>

Yes, these steps look good.

I don't like thinking. Up to now I need to think if I need to decide if 
data is sensitive or unneeded.

It would be nice if this could be defined somehow. I think per row is not 
useful, but per table looks feasible.

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/70054b6b-281d-4690-a0f7-2fbd0993c6ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Setting up a system for testing by users (tables are tables?)

2018-08-13 Thread Mikhailo Keda
1. take a dump of production db
2. remove/anonymize all sensitive or unneeded data (you can use django 
admin or sql or python script)
3. reduce amount of data if needed
4. take a git branch with fixes 
5. make sure there are no sensitive data in your code

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/b48a127f-ac71-47a6-a9c3-8cad9266b1f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Setting up a system for testing by users (tables are tables?)

2018-08-11 Thread Derek
*The users who should do the testing say "The new system should be like the 
production system."*
You need to let them know ASAP that that is very unlikely to be the case, 
unless you are using exactly the same tools.  You can probably provide 
similar functionality.

Otherwise you are too vague to give better feedback - "copying a system" 
has too many meanings.  If its just the database you need, and you plan to 
write a new front-end from scratch using Django, then that is "do-able" 
(assuming you can extract the data from SAP - that is a problem you will 
need to ask the SAP experts about).  Once you have the database available, 
you can follow this guide:

https://docs.djangoproject.com/en/2.1/howto/legacy-databases/


On Wednesday, 18 July 2018 11:45:00 UTC+2, guettli wrote:
>
> I have a task which looks simple at the first sight:
>
>  Setting up a system for testing by users. 
>
> In my case it is a custom issue tracking system.
>
> The users who should do the testing say "The new system should be like the 
> production system."
>
> If this would be true, then dump+restore of the database should work.
>
> No Nr2: the production system contains a lot of issues, and these should 
> not be in the new system.
>
> No Nr2: The production system contains configuration (in the database) of 
> remote storage systems. These
> database rows must not get copied, otherwise the testing system would 
> transfer testing data
> to the production storage system.
>
> Configuration like the list of ticket types should get copied.
>
> Tables are tables, or is there a difference between tables?
>
> Up to now I only found one hint to this task: In SAP this is called 
> "client copy" and there seem
> to be different "delivery classes" of a table:
>
>
> https://help.sap.com/doc/saphelp_crm70/7.0.0.18/en-US/43/45860774b711d2959700a0c929b3c3/content.htm?no_cache=true
>
> Are there tools/framework which support copying a system? I am curious, if 
> you know a framework outside django, please tell me.
>
> Up to now I could not find a tool or hint about solving this in a reusable 
> way in django. If I was blind, please let me know.
>
> Any kind of feedback is welcome.
>
> Regards,
>   Thomas Gütler
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8508f0bd-e5f6-4401-9215-682bb39ee5a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Setting up a system for testing by users (tables are tables?)

2018-08-10 Thread guettli
I see: no reply. Why?

Am Mittwoch, 18. Juli 2018 11:45:00 UTC+2 schrieb guettli:
>
> I have a task which looks simple at the first sight:
>
>  Setting up a system for testing by users. 
>
> In my case it is a custom issue tracking system.
>
> The users who should do the testing say "The new system should be like the 
> production system."
>
> If this would be true, then dump+restore of the database should work.
>
> No Nr2: the production system contains a lot of issues, and these should 
> not be in the new system.
>
> No Nr2: The production system contains configuration (in the database) of 
> remote storage systems. These
> database rows must not get copied, otherwise the testing system would 
> transfer testing data
> to the production storage system.
>
> Configuration like the list of ticket types should get copied.
>
> Tables are tables, or is there a difference between tables?
>
> Up to now I only found one hint to this task: In SAP this is called 
> "client copy" and there seem
> to be different "delivery classes" of a table:
>
>
> https://help.sap.com/doc/saphelp_crm70/7.0.0.18/en-US/43/45860774b711d2959700a0c929b3c3/content.htm?no_cache=true
>
> Are there tools/framework which support copying a system? I am curious, if 
> you know a framework outside django, please tell me.
>
> Up to now I could not find a tool or hint about solving this in a reusable 
> way in django. If I was blind, please let me know.
>
> Any kind of feedback is welcome.
>
> Regards,
>   Thomas Gütler
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/0949314c-189f-4e90-b4f0-802ffe7de7fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Setting up a system for testing by users (tables are tables?)

2018-07-18 Thread guettli
I have a task which looks simple at the first sight:

 Setting up a system for testing by users. 

In my case it is a custom issue tracking system.

The users who should do the testing say "The new system should be like the 
production system."

If this would be true, then dump+restore of the database should work.

No Nr2: the production system contains a lot of issues, and these should 
not be in the new system.

No Nr2: The production system contains configuration (in the database) of 
remote storage systems. These
database rows must not get copied, otherwise the testing system would 
transfer testing data
to the production storage system.

Configuration like the list of ticket types should get copied.

Tables are tables, or is there a difference between tables?

Up to now I only found one hint to this task: In SAP this is called "client 
copy" and there seem
to be different "delivery classes" of a table:

https://help.sap.com/doc/saphelp_crm70/7.0.0.18/en-US/43/45860774b711d2959700a0c929b3c3/content.htm?no_cache=true

Are there tools/framework which support copying a system? I am curious, if 
you know a framework outside django, please tell me.

Up to now I could not find a tool or hint about solving this in a reusable 
way in django. If I was blind, please let me know.

Any kind of feedback is welcome.

Regards,
  Thomas Gütler

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/4b410060-3acc-4ddc-87c3-aa9c2af750c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.