Basically am from QA department and have good experience in software testing. Recently committed in AEM technology project and am new to AEM. Can you please share the questionnaire / things i need to look before going for testing?
As AEM based on components and services so you should first learn the basic terminology about AEM. For that you go through the helpx documents.
Also here is the link to the unit testing framework
Related
I am trying to build a desktop app.
I am thinking of using electron on the recommendation of a web-developer friend of mine, but as I am the only sole developer, I don't have the means to test the software on different platforms(OS, hardware etc.).So I am anticipating that this will cause a problem later, in the end, to test/debug software on different platforms and different OS.
I have ruled out web-apps because of some privacy concerns of the users for the remote data hosting.
Software is pretty lightweight and is almost equivalent to the image viewer apps with some slight modifications.
How to solve the problem of variations of different platforms?
Any literature suggestions pointing me in the general direction are also welcome.
Sometimes it helps to think of Electron as two processes.
The renderer vs the main processes. Generally the renderer process which runs the HTML/CSS/JS is it's own isolated component, and you communicate to the main process using IPC.
So generally for the UI, you can use mostly any web based testing framework to test reliability. At Amna, for example, we use Cypress as our E2E testing platform. You an also use something like QAWolf. Both should work with localhost. In general, most website testing tools should work fine, and consistently across platforms.
Where this gets tricky is when a UI functionality makes a call to the OS or the main process. For example, saving to the disk, or launching a program.
The general flow is this, and I've yet to find radically simpler options:
Set-Up a VM or buy a machine with the corresponding OS. I used Spot VMs in Azure for this.
Manually test the scenarios you care about in each VM before you ship
If you have a lot of cases that rely on the OS, then you should be able to further optimize this by using an automated test runner like Spectron.
From experience, what I've realized is that most of the iterations I do happen more on the UI than the underlying functions with the cross-platform capabilities. And if your code has good separation (e.g. contextIsolation:true, nodeIntegration:false), it should be pretty obvious when you need to do an entire "cross-platform" test vs just UI tests.
I'm not familiar with a lot of large-scale electron testing frameworks, I do know that ToDesktop handles package building and generating binaries to perform a smoke test and verify things open across different operating systems.
It depends.
The answer depends on what you are building, so it makes sense to figure out what you actually want to build. Some questions you might ask yourself:
Do I need a database?
Do I need authentication?
Do I need portability?
Do I need speed to market?
Do I want to pick a language I'm familiar in?
These are all good questions and there are dozens more we all ask ourselves. However, back to your original question.
Electron is a fine choice
Yes, there are alternatives. But Electron is used for Visual Studio Code, Facebook Messenger, Microsoft Teams and Figma. Choosing Electron means there are other developers making apps and there are proven apps in the market so you don't have to worry about a dead ecosystem.
Electron is easy to onboard if you know web technologies, think js, html and css. If you know these, you can transfer your web dev knowledge and make a cross-platform app. You don't have to worry about learning each OS since the UI is the webpage which will look mostly* the same between each OS. (*some very minor differences, but essentially the same).
Cross-platform deployment is easy
There are a few ways of bringing your app to multiple platforms, I happen to be most familiar with electron-builder, but the other two solutions work as well.
Many templates to start with
I am biased, since I'm the author of secure-electron-template which is one of the many templates you can choose from when starting an app. However, I recently reviewed all Electron templates and found that only 4 do not have serious security vulnerabilities.
The Electron framework frequently is updated, and over the course of the past few years there has been a shift in the way Electron apps are made. Some earlier frameworks didn't have good secure defaults which some of the older Electron templates inherited and thus, aren't as secure as new frameworks that follow security guidelines.
If you decide on Electron, give my template a try. It's got a number of features I'm building out in order to help the community with features they might want (ie. internationalization (i18n), saving local data, custom context menus, page routing, e2e unit testing, and how one can use license key validation, to name a few things).
I have uploaded some MadCap Flare online help files into my SVN repository. What code does the web developer use to get these help pages into the online help of the web application?
On their website, MadCap Software provides a context sensitive help guide for Flare. It should show you what the technical writer and what the developer has to do to link the help system to the application, depending on which type of help output you are creating. You can find it here: http://docs.madcapsoftware.com/flare2018/FlareCSHGuide.pdf.
Fair warning, so far I have no experience with the information provided in the guide, as our CHM help system was already up and running when I started working on our Flare project, so I've never initially linked a Flare project to an application, just updated an existing project (therefore the "should show you").
If you have further questions about Flare, the peer-to-peer support forum (https://forums.madcapsoftware.com) is usually a really good resource. There are a couple of very active users there that really know the ins and outs of Flare. Might be worth it to go over there for Flare specific information, as Flare is a niche tool probably only known to few here on stackoverflow, but it's the bread and butter for the guys and gals over in the MadCap forums.
I am working in a team responsible for development and maintenance of an enterprise web solution project where the front end customer portal is developed with PHP on Yii framework and backend web application for back office operations is developed with Python on OpenERP.
We are trying to automate the test workflows using only open source test automation tools are looking at options like Selenium,DalekJS.
My question is, keeping my project in mind which tool would be ideal to easily automate test workflows with a great test coverage and easy maintainability. We might have regular enhancements and fixes for both customer portal and back office web application. Which tool would be better keeping my project in mind, is it Selenium or DalekJS?
Any inputs/feedback or past experience would be quite helpful.
Hi Shashi Vardhan Andem,
unfortunatly it seems DalekJS is dead, unmaintained dependencies, last commit 2 years ago. We recently switched from dalekjs to http://webdriver.io/
So to answere your question. Definitly Selenium because it's gonna be still developed.
Cheers,
Dennis
In a nutshell: is RadPHP a toy? or can you build real web sites, such as a e-commerce/shopping carts app that will:
Support 100s of simultaneous users on a reasonably good web server, like any other PHP app
my specific concern is the RPCL library might be bloated and inefficient
Be easy to assign the CSS hooks and integrate CSS files supplied by designers
Be as easy as 'plain' PHP programming is to talk to external sites such as payment gateways
Easily integrate third party components; Javascript and PHP e.g. Lightbox, eg CKEditor.
I am coming from a Delphi background, not PHP, so please excuse my ignorance and trouble at evaluating RadPHP XE2's potential as an easier way to transition to web development without sacrificing potential to scale.
It has a demo app created for oscommerce the well known open source e-commerce app.
Yes
No appearent barrier.
It already has components integrating 3rd party stuff such as zend, qooxdoo, jquery etc..
I'm also coming from delphi background with almost no php. Currently I'm developing a prado framework based ERP application using eclipse as ide. On my leisure time I'm toying with radphp, and I think we could have used it as well as the eclipse-prado kit but I'm in no place to make the decision. In my experience radphp is developing well into form. The first releases / versions were really sluggish. But XE2 looks solid. If vcl for php is fine tuned for performance in the future releases, radphp will have better days.
I'm looking at the tools (Test Telerik WebUI Studio, Visual Studio 2010 Test Professional) to automate testing web applications written in NET. Do you use such tools? If so, what tools are you using and what experience do you have with this type of testing. Particularly I am interested in issues of maintenance of such tests (for example, if you change layouts.)
Disclaimer: I work for Telerik; I'm just sharing the relevant resources for the WebUI Test Studio
Regarding the WebUI Test studio, there's a free 30-day trial that you can try yourself. There's a weekly live demo, and you can even request a free personal demo. Any of these might give you further insight whether the product will be suitable for your environment and might answer relevant questions.
Regarding the test-case maintenance, there is a detailed feature overview on the product site.
I hope this helps!
Go for CodedUI.It comes along with VSTS 2010 Ultimate.
The search criteria will continue to work even if you chnage the layout