Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

How do you test your application?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    How do you test your application?

    Hello,
    I have 2 questions.
    1-I upgraded the version of alpha, I just have 1 server (not alpha cloud) how do you test your application on the new version?
    Do you install a new instance of the version? how will SSL work then?

    2-how do you test the modifications or improvement you make? In alpha there is no unit test that I am aware of.
    do you use any methodology or you just do "basic test" Run the updated module and try it.
    This what I do now, but sometimes I am having issues with the live app.

    Any input will be nice, it is always nice to know how others are doing it :)


    Thank you,

    #2
    Big subject Paul.
    I don't do Alpha Web but have run some big test teams in government intranet apps.
    There are a few levels, but the first thing to draw is an INTERFERENCE MODEL.
    What that should show you is where one table or process is dependent upon another. Change one and you need to check the other.
    Next, levels of testing.
    Desk check. Like reviewing your code for typos.
    Functional check. The code works at this level.
    Linked testing. Does what I have done affect the next level .This is where the IM comes in.
    System test. Follow the changes through to completion.look at all results.
    Regression test. Full blown test starting from documented data with written expected results and reentered on a virgin system. Rare, but sometimes necessary.

    Writing out test dialogs is always useful as they can be followed explicitly and you know what results are expected and you can identify a bug more easily if the expectations are not met.

    Then, The Idiot Test. Give the app to someone with no knowledge of it. See what havoc they can wreak!

    I always found that people closest to the app skip the detailed testing as "of course it's OK, I wrote it".

    In life critical stuff, that won't wash.
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Giving advice is dangerous.
    Giving "Good Advice" can be fatal.

    Comment


      #3
      OK, so I am probably too brave for doing it this way but here goes - for a new "component" the first thing I do is actually test out the component with my data live on the server with security settings such that ONLY I can see it - then if all goes well I open it up to everyone else and see what happens. For a new server version, I simply install it use a few of the critical components, then see what happens. One of the best things about AA is I can so easily roll back to the previous WORKING version if I see something critical that I cannot fix due to a bug or some other anomaly.
      I always send an announcement that the server software has been updated - users are well aware that things can be wonky the first few days or NOT. Most often of late it's been a date issue, or a button doesnt seem to work. Users know what is supposed to be happening and I get a call immediately when things are off. Again, I can roll back very quickly and users know what to expect when theres a server update.
      NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

      Comment


        #4
        Luv it!
        The "suck it and see" approach.
        There is realy no failsafe and warning friendly users is a great idea.
        I've had stuff tested to destruction, go live, and Mandy Lifeboats in Social care completely stuffs it.
        See our Hybrid Option here;
        https://hybridapps.example-software.com/


        Giving advice is dangerous.
        Giving "Good Advice" can be fatal.

        Comment


          #5
          Originally posted by Ted Giles View Post
          Luv it!
          The "suck it and see" approach.
          There is realy no failsafe and warning friendly users is a great idea.
          I've had stuff tested to destruction, go live, and Mandy Lifeboats in Social care completely stuffs it.
          That's why I asked the question, 😀
          I found out the best test is to do a demo of the app.
          That's why I demo my app to an imaginary person 😀😃. While doing it I take note of the issues and we reschedule 😉

          Comment


            #6
            I have imaginary friends too
            See our Hybrid Option here;
            https://hybridapps.example-software.com/


            Giving advice is dangerous.
            Giving "Good Advice" can be fatal.

            Comment


              #7
              I too demo to imaginary clients.

              I use IIS for my server. I have a second IIS website setup as dev.(domain).com and got a cheap ssls.com certificate for a few bucks just to make everything work. I'll publish to that first, test it all out, then publish to the production site if everything is good.

              Comment


                #8
                That's interesting. I have a temporary url set up and when it's OK, port it to my domain name with the SSL.
                See our Hybrid Option here;
                https://hybridapps.example-software.com/


                Giving advice is dangerous.
                Giving "Good Advice" can be fatal.

                Comment


                  #9
                  I have a couple things that won't work without the SSL. That's the only reason I have the certificate for the dev site.

                  Comment


                    #10
                    Got it. Some browsers won't accept a temp url.
                    I also have a Demo setting which does everything except any actual data transactions in the app.
                    Do you use Cloudflair?
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/


                    Giving advice is dangerous.
                    Giving "Good Advice" can be fatal.

                    Comment


                      #11
                      No, I don't use Cloudflair. I manage all my own servers, etc. I have an AWS server of my own with IIS and my own SQL server. Security is open to what I need it to do.

                      Comment

                      Working...
                      X