It would be great to have a version control system for Filemaker scripts where we can view all previous revisions and revert back . Or some way if we will be able to push/pull the code like GIT SCM.
Yes! In the meantime, I will:
Print script(s) to PDF time stamped.
duplicate a script and append “_BAK_<<ts>>” to the name.
All before making major changes. The second one, of course, has the Revert (although manually)
Sent from miPhone
PS you must vote for your own idea. It is not automagically done for you upon creation.
If somehow all scripts got deleted , then we can not revert it back.
I am asking for above scenario.
And why we should duplicate script each time we modify it.
Developers should focus on writing script only. It should create revisions automatically. [May store it remotely]
That is what a backup is for! I get what you are after however there aretooc many variables Sometime between scrip versions field names layouts and others like other scripts get altered as well. DO you want all that roll back when you go back to an ealrier script? Or do you want the earlier script to be broken on reinstatement?
With what Bev suggest (and I do as well) at least nomenclature stays however other things often down work with a straight revert! nature of the beast so to speak!!
You are backing up the file, right? If you Delete all scripts, versioning would not solve the problem. See the Roadmap for what might be.
Actually backup contains whole binary version of file. I want revisions of scripts as files/ a dropdown in FileMaker scripting space. The whole idea is to have a source code management feature internally. [Not as a backup]
Scripts can be pushed /pulled to remote locations like bitbucket/github etc .
Let me explain what i want .
1. Script revisions to be shown on each save action of script. It should be available either in FileMaker scripting space or in some folder as xml file/ something like that.
2. Whenever i want , i should be able to choose to revert back to previous version.
3. I should be able to see the difference between the scripts as GIT/SVN diff tool. It will help me to analyze what are the changes done in new version and what i missed.
Please correct me if i am wrong .
I will be happy to get suggestions from experts like you.
Currently, we are exporting all scripts as .txt files from DDR and then commit them automatically into our SCM.
Do you think, FileMaker needs to have automated process for storing revisions of scripts in remote locations/GIT whatever ?
If yes , please vote my idea.
Its a time consuming process to generate DDR each time.
The ideas must be allow us to vote up, down (or not vote), in addition the comments are meant to clarify exactly what the idea means to you (OP) or others. Your replies are also valid. That is how the ideas get 'fleshed out' to let the PMs (Project Managers) know what is needed, why it is needed, and how much it is needed (by votes). Let the discussion continue and vote as desired!
Thanks a lot beverly for your quality words.
Lets hope for a positive response from FileMaker team.
I posted an idea last year. But not sure whether it has been noticed by FM guys or not.
Automated testing tool for FileMaker desktop apps, CWP enhancements , Plugin development clear documentation etc.
I'm very confident that ALL ideas are read. There is, however, no "promise" that they will be delivered (or even in the way we thought they might be). See the full information on this space:
https://community.filemaker.com/docs/DOC-6450 About the Product Ideas discussion space
You are correct.
The PMs of FMI do read every single product idea and comment, so you can be sure this is being read, as well as your other idea.
Geist Interactive, the company for who I work, does a lot with testing in FileMaker. Here's a post about it:FileMaker Testing, Part 1 - Your First Test - Geist Interactive
Additionally Lance Brandenberg will do a DevCon presentation about Testing. If you are able to come, check out his session.
Thank you for sharing the links.
The testing methods like TDD
<https://en.wikipedia.org/wiki/Unit_testing> are more related to
developer level testing.
In that product idea, i am asking for a way in which QA engineer can do
automated testing .
Ex : Selenium
Please let me know if you are aware of any automation tools like
selenium which can be used to test FM apps externally from QA point of
Unit testing is pretty straightforward to implement in FileMaker. This screenshot provides a truncated example - the script has close to 100 tests in it. It's saved a vast amount of time by highlighting regression problems as soon as they happen. You can also do unit testing for Custom Functions, though I suspect very few people bother.
Unfortunately I'm not aware of anything like Selenium that would run on a FileMaker solution.
The single binary file containing schema, layouts, code, and data is both a blessing and a curse. It gives us a tightly integrated environment that's really quick for development. The downside is that we don't get migrations like you get in environments like Rails or Phoenix - check the FileMaker product road-map on this point. Limited ability for version control. No tools for DevOps unfortunately. But like all things it's a trade-off. On balance it's worth it for a number of our internal systems.
Hmm. It seems like we need to depend upon unit testing as per now.
Using c++, FileMaker user interactions can be automated.
Initially i developed one node js app where i used to click on some
buttons / close some windows by moving mouse cursor to a specific
co-ordinate of computer screen. I used c++ addon of node js for managing
But all those co-ordinates were hardcoded and it has not worked if
someone will resize the FM app window.
So as FileMaker has been be developed using c/c++ internally , i hope ,
they can develop such tools to automate user actions on FM objects.
Do you think, FM automation testing is a necessity if we are developing
large enterprise apps ? Please let me know your thoughts.
In this platform, i got the opportunity to share my ideas with all of
you. I am open to constructive criticism as always.
Could you use the design functions to grab the locations of the on-screen objects? That might work though I suspect it would be really clunky though. The development effort to do that predictably and reliably would be significant. I can't imagine any way that the cost would outweigh the benefit.
I like this idea. There could be some sacrifices if the versioned data is stored externally, away from dependences that may be renamed over time. Check out this similar idea, but as an internal version management type thing Script Meta Data
I feel if it was done it would HAVE to be external or it would risk field size bloat!
Retrieving data ...